linux-kernel - Re: 2.6.18-rc5-mm1, make oldconfig from 2.6.18-rc5 destroys LVM

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:	Sat, 2 Sep 2006 18:40:54 -0700
From:	Andrew Morton <akpm@...l.org>
To:	"John Stoffel" <john@...ffel.org>
Cc:	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.18-rc5-mm1, make oldconfig from 2.6.18-rc5 destroys LVM

On Sat, 2 Sep 2006 20:49:04 -0400
"John Stoffel" <john@...ffel.org> wrote:

> 
> Andrew,
> 
> When I do a make oldconfig under 2.6.18-rc5-mm1, with my working
> 2.6.18-rc5 .config file (appended below), all the LVM and MD stuff
> gets blown away silently.  It looks like the drivers/md/Kconfig didn't
> get updated properly when it was tweaked, possibly the new options to
> get rid of BLOCK devices, or the ripping out of LVM1 stuff.
> 
> It looks like instead of 'if CONFIG_BLOCK' at the top, it just needs
> to be 'if BLOCK' instead.  

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.18-rc5/2.6.18-rc5-mm1/hot-fixes/
contains a fix for this.

> And I'd really suggest that it NOT be this silly name BLOCK, something
> more meaningful, like USE_BLOCK_DEVICES or something equally useful to
> parse.

mm...  I think CONFIG_BLOCK is a reasonable compromise between the needs for
brevity and understandability.

-- 
VGER BF report: H 0.277375
-
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/