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
| ||
|
Date: Wed, 5 Mar 2008 01:19:45 +0000 From: Alasdair G Kergon <agk@...hat.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Ingo Molnar <mingo@...e.hu>, kay.sievers@...y.org, Greg KH <gregkh@...e.de>, linux-kernel <linux-kernel@...r.kernel.org>, "Rafael J. Wysocki" <rjw@...k.pl>, Alexey Dobriyan <adobriyan@...ru>, dm-devel@...hat.com, "Zhang, Rui" <rui.zhang@...el.com>, Linus Torvalds <torvalds@...ux-foundation.org> Subject: Re: [dm-devel] Re: 2.6.25-rc regression: kernel panic on boot On Tue, Mar 04, 2008 at 10:43:12AM -0800, Andrew Morton wrote: > 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. It's not a device-mapper problem: It's between userspace LVM2 and kernel sysfs. LVM2 userspace expects a particular sysfs layout. That layout got changed without offering sufficient lead time (>6-9 months) for the required userspace changes to propagate into the main versions of the distros people use. LVM2 userspace version 2.02.29 (released 5th December 2007) can handle old and new layouts. The patch was in the CVS head for a while before that. Earlier versions of LVM2 require CONFIG_SYSFS_DEPRECATED. A less-efficient workaround is to disable the use of sysfs in the LVM2 config: 'devices { sysfs_scan = 0 }'. (I think the root cause of this mess was changing what CONFIG_SYSFS_DEPRECATED did instead of adding a new setting that could be enabled by default.) Alasdair -- agk@...hat.com -- 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/
Powered by blists - more mailing lists