linux-kernel - Re: [bisected] broken make-kpkg kernel build in 3.15-rc1

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:	Tue, 15 Apr 2014 15:10:44 -0400 (EDT)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
cc:	Christoph Lameter <cl@...ux.com>, Michal Marek <mmarek@...e.cz>,
	Vince Weaver <vincent.weaver@...ne.edu>,
	linux-kernel@...r.kernel.org, Jason Cooper <jason@...edaemon.net>,
	Grant Likely <grant.likely@...aro.org>,
	Rob Herring <robh+dt@...nel.org>
Subject: Re: [bisected] broken make-kpkg kernel build in 3.15-rc1

On Tue, 15 Apr 2014, Russell King - ARM Linux wrote:

> Right, so the thing to do is to run a build with the commit applied,
> without any -j arguments and V=1, logging the output (so that predictable
> output can be generated).
> 
> Then run the same thing with the commit reverted, again logging it.  Then
> diff the two and see what's different.

OK, I captured the output.  No diffs, as of course reverting things
means one kernel was called 3.15-rc1 and one 3.15-rc1+ which meant more or 
less every line changed.

It seems that on stock 3.15-rc1 (which fails to build) after running 
depmod it kicks into

	restore_upstream_debianization

which goes down a path which causes the file permission failures

Wheras 3.15-rc1 with the problem commit reverted this doesn't happen.

This is a really weird bug, I've tried reverting individual hunks of the 
problem commit manually and it is not clear at all to me what is 
triggering this.

Vince

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