linux-kernel - Re: linux-next: Tree for Apr 26

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: <517A615D.9020400@suse.cz>
Date:	Fri, 26 Apr 2013 13:13:33 +0200
From:	Michal Marek <mmarek@...e.cz>
To:	sedat.dilek@...il.com, "Yann E. MORIN" <yann.morin.1998@...e.fr>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-kbuild@...r.kernel.org
Subject: Re: linux-next: Tree for Apr 26

On 26.4.2013 13:08, Michal Marek wrote:
> On 26.4.2013 12:49, Sedat Dilek wrote:
>> With reverting all kbuild-next commits I was able to build again.
>>
>>       Revert "kconfig: implement KCONFIG_PROBABILITY for randconfig"
>>       Revert "kconfig: allow specifying the seed for randconfig"
>>       Revert "kconfig: fix randomising choice entries in presence of
>> KCONFIG_ALLCONFIG"
>>       Revert "kconfig: do not override symbols already set"
>>       Revert "kconfig: fix randconfig tristate detection"
> 
> I did the same, then applied all the kconfig commits once more and did a
> git bisect with this script:
> 
> #!/bin/sh
> 
> cp config-bad .config
> make silentoldconfig </dev/null
> 
> This resulted in
> 
> 7ded2624f8988bd22819a60a6000ba6b7091db89 is the first bad commit
> commit 7ded2624f8988bd22819a60a6000ba6b7091db89
> Author: Yann E. MORIN <yann.morin.1998@...e.fr>
> Date:   Sun Mar 10 16:34:10 2013 +0100
> 
>     kconfig: fix randomising choice entries in presence of KCONFIG_ALLCONFIG
> 
> The commit id is different, because it is reverted and applied again. Yann?

Commit 422c809 ("kconfig: fix randomising choice entries in presence of
KCONFIG_ALLCONFIG") reverts cleanly and reverting it fixes the bug. So
there is a plan B.

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