linux-kernel - Re: Linux 2.6.35

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4C59CA4F.4090003@garzik.org>
Date:	Wed, 04 Aug 2010 16:15:11 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Donald Parsons <dparsons@...ghtdsl.net>
CC:	Harald Hoyer <harald.hoyer@...il.com>,
	Bjorn Helgaas <bjorn.helgaas@...com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Linux 2.6.35

On 08/02/2010 10:31 PM, Donald Parsons wrote:
> Using your suggestion as to where the problem lies, I investigated
> more deeply and found:
>
> I've now got 2.6.35-rc6-git3 to boot (and almost certainly 2.6.35 final)
>
> Make oldconfig broke at the transition where boot began failed, ie,
> between 2.6.34-git4 and 2.6.34-git5.   Even though modules are the
> same, boot fails.  If I use gconfig and set CONFIG_SATA_AHCI=y
> instead of CONFIG_SATA_AHCI=m it works, except cannot select =y
> unless CONFIG_ATA changed from m to y.
>
> So at some point in past, make oldconfig had apparently changed
> CONFIG_SATA_AHCI from y to m and system still booted.  But between
> 2.6.34-git4 and 2.6.34-git5 the ability to boot was lost.
>
> So make oldconfig is not 100% trustworthy in this case.  I do not
> know if this is a problem that should be fixed.  Ask if you want
> any .config diffs.


The modules are not necessarily the same:  "libahci" was introduced in

	commit 365cfa1ed5a36f9bcb9f64c9f0f52155af2e9fef
	Author: Anton Vorontsov <avorontsov@...mvista.com>
	Date:   Sun Mar 28 00:22:14 2010 -0400

	    ahci: Move generic code into libahci

so there exists the possibility that the initramfs builder, or whatever 
is being used to load your ATA drivers, missed this dependency.  Modern 
initramfs builders should be able to figure out module dependencies, so 
this /shouldn't/ be an issue...  but it might be.

	Jeff



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