linux-kernel - [kbuild regression, post-rc1] Remote installation over read-only NFS broken

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <201006071110.26245.rjw@sisk.pl>
Date:	Mon, 7 Jun 2010 11:10:26 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Michal Marek <mmarek@...e.cz>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [kbuild regression, post-rc1] Remote installation over read-only NFS broken

Hi Michal,

Unfortunately, your commit 73d1393eb8507ed5fd7f8e696f6b1ecc18035ebe
(kbuild: Generate modules.builtin in make modules_install) broke my testing
environment that had always worked before.

Namely, I build kernels on a central machine and export the build directory
along with the kernel sources over read-only NFS to test boxes.  Then, on the
test boxes I run "make modules_install", copy the kernel to /boot, run mkinitrd
and so on.  Now, after your commit above the "make modules_install" command on
the test boxes doesn't work any more, because it tries to write to the build
directory, which is mounted read-only.

Please fix or revert.

Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/