linux-kernel - Re: Strange linux-next build error

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] [day] [month] [year] [list]

Date:	Sun, 4 May 2008 07:36:39 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Daniel Hazelton <dhazelton@...er.net>
Cc:	Ingo Molnar <mingo@...e.hu>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	LKML <linux-kernel@...r.kernel.org>,
	Pavel Machek <pavel@...e.cz>, linux-next@...r.kernel.org
Subject: Re: Strange linux-next build error

On Sat, May 03, 2008 at 09:37:07PM -0400, Daniel Hazelton wrote:
> On Saturday 03 May 2008 18:40:18 Ingo Molnar wrote:
> > * Daniel Hazelton <dhazelton@...er.net> wrote:
> > > > Can you try to do a:
> > > > make V=1 and post the output a few screen fulls before and until
> > > > the bug triggers.
> > > > They I will see if I can work out what is happening.
> > > >
> > > > Thanks,
> > > > 	Sam
> > >
> > > I've been unable to trigger it with "make V=1 bzImage" - does the
> > > verbosity change, somehow, the default number of makes that get run ?
> > >
> > > If it does, I could try adding -j2 or similar to see if that causes it
> > > to trigger.
> >
> > try something like:
> >
> >    make -j2 V=1 bzImage >log.txt 2>&1
> >
> > and see whether the error shows up in log.txt. Console output caused by
> > the increased verbosity (especially if it's a slower console like an
> > xterm) can hide build races.
> >
> > 	Ingo
> 
> And this appears to have been a false alarm. For the tests I did a clean pull 
> of the tree and started the build. When I kept *NOT* getting a build error on 
> the clean tree I started checking permissions and, while the files that this 
> error was happening for (and the containing directory) all had good 
> permissions, the correct ownerand all that - so I didn't look deeper. On 
> doing a deeper look it seems that there were some files and directories that 
> belonged to "root" and had 0644 for permissions.
> 
> After doing "make mrproper" and the reconfiguration I reset the owner/group on 
> the entire tree of files to be non-root and the build (at -j4) has finished 
> without a problem.
> 
> Sorry about that.

But this makes sense. We have/had a problem where we always rebuilded
wakeup.lds. So if you by accident have done "make bzImage" as root this
file would have been generated and thus belonging to root.
x86.git has the fix for this so we no longer do the wakeup.lds rebuild
for each kernel build and I expect it to hit both -next and -lins soon.

And I am very happy to nail down why - because having to much unexplained
issues with the build system will decrease the trust in it. And there I
do not want to go with kbuild - it helps no one.

Thanks for your feedback!

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