linux-kernel - Re: 2.6.25-rc regression: kernel panic on boot

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: <20080304193348.GC5534@suse.de>
Date:	Tue, 4 Mar 2008 11:33:48 -0800
From:	Greg KH <gregkh@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, "Zhang, Rui" <rui.zhang@...el.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	kay.sievers@...y.org, "Rafael J. Wysocki" <rjw@...k.pl>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Alexey Dobriyan <adobriyan@...ru>, dm-devel@...hat.com
Subject: Re: 2.6.25-rc regression: kernel panic on boot

On Tue, Mar 04, 2008 at 10:43:12AM -0800, Andrew Morton wrote:
> On Tue, 4 Mar 2008 14:54:47 +0100 Ingo Molnar <mingo@...e.hu> wrote:
> 
> > * Greg KH <gregkh@...e.de> wrote:
> > 
> > > On Mon, Mar 03, 2008 at 07:25:49AM +0800, Zhang, Rui wrote:
> > > > Hi, all,
> > > > 
> > > > kernel panic on boot when I try to run 2.6.25-rc1 and later, but 2.6.24-rc8 boots okay.
> > > > The result of git-bisect shows that
> > > > edfaa7c36574f1bf09c65ad602412db9da5f96bf is first bad commit.
> > > > 
> > > > The git-bisect-result and the dmesg log when the kernel panic are 
> > > > attached. Any help on this please? :)
> > > 
> > > Are you using LVM?  If so, please either upgrade your userspace/initrd 
> > > stuff, or enable CONFIG_SYSFS_DEPCRECATED
> > 
> > we _really_ must handle this differently and this _is_ a regression that 
> > multiple people have spent hours on bisecting already ...
> > 
> > So "enable CONFIG_SYSFS_DEPCRECATED" is _NOT_ the right answer, and this 
> > has been pointed out to you in the past.
> 
> Isn't the device-mapper kernel code capable of detecting the older userspace
> version and loudly warning about it?  That at least would prevent us from
> wasting lots of people's time like this.

Yes, this is an LVM issue with older userspace provided by some
distros, I think the dm code can notify the user about the problem, Kay
would know more.

The two distros I use here work just fine with this set to N :)

I have a patch queued up to change the wording of this config entry to
not say 2006, as that's not true anymore, and it should hopefully fix
some of the confusion here.

thanks,

greg k-h
--
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/