linux-kernel - Re: 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again...

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:	Thu, 07 Jun 2007 15:44:56 +0900
From:	Tejun Heo <htejun@...il.com>
To:	Valdis.Kletnieks@...edu
CC:	Andrew Morton <akpm@...ux-foundation.org>,
	Greg Kroah-Hartman <gregkh@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.22-rc4-mm1 - 'lvm vgscan' busticated again...

Valdis.Kletnieks@...edu wrote:
> On Wed, 06 Jun 2007 02:07:37 PDT, Andrew Morton said:
>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc4/2.6.22-rc4-mm1/
> 
> This one died a horrid death at boot time - console log indicates it found the
> hard drive OK, found the 2 partitions on it.  But when the initrd ran a
> 'lvm vgscan', it didn't find the LVM2 space on /dev/sda2, so it panic'ed when
> it fell off the end of the initrd because the root= wasn't there.
> 
> My first guess for blame:
> 
> gregkh-driver-sysfs-allocate-inode-number-using-ida.patch
> 
> as that's awfully similar to gregkh-driver-sysfs-fix-i_ino-handling-in-sysfs.patch
> that broke 'lvm vgscan' for me in the same way on 21-rc7-mm[12].
> 
> I'll hopefully get a chance to revert that one and test later today - a quick
> 'patch -p1 -R --dry-run' shows a number of conflicts that will need hand-fixing
> at the very least.

Did rc3-mm1 work?  Can you find out the first broken -mm?

Thanks.

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