linux-kernel - Re: Linux v2.6.27-rc1: problem with firmware stuff

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]

Message-Id: <1217370397.27925.139.camel@pmac.infradead.org>
Date:	Tue, 29 Jul 2008 23:26:37 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Linux v2.6.27-rc1: problem with firmware stuff

On Tue, 2008-07-29 at 14:01 -0700, Linus Torvalds wrote:
> 
> On Tue, 29 Jul 2008, Rafael J. Wysocki wrote:
> > 
> > Actually, this happened due to some firmware files being created as root during
> > installations of pre-rc -git kernels from the O= directory.  So, not a real
> > problem, but somewhat confusing.
> 
> Yeah, I've had that happen myself. It used to be that "make 
> modules_install" (as root, obviously) would try build a new version of the 
> kernel, and as a result subsequent build attempts would fail horribly 
> because of various random files being now owned-by-root.
> 
> I don't know if there is a whole lot we can do about it in general..

Not in general. I _think_ I fixed the specific problem which led to
Rafael's situation, but I'm still waiting for confirmation of that.

-- 
dwmw2

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