linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 Jun 2010 07:41:42 -0700 (PDT)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
cc:	Michal Marek <mmarek@...e.cz>, LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [kbuild regression, post-rc1] Remote installation over read-only
 NFS broken



On Mon, 7 Jun 2010, Rafael J. Wysocki wrote:
> 
> 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.

Ahh. It's broken for another reason too. Even if it's a writable 
filesystem, it means that there's a lot of files that get written by root 
(since you have to be root to do the install). Which is very 
uncomfortable, and we've tried very hard to avoid that.

So it _should_ be possible to do a build as a normal user, and then do the 
install as root, and afterwards

	find . -user root

should return the empty set (which in practice ends up being basically the 
same thing as Rafaels requirement that it work on a read-only build).

			Linus
--
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/