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] [day] [month] [year] [list]

Message-ID: <17658.15935.903687.325991@smtp.charter.net>
Date:	Sat, 2 Sep 2006 22:30:23 -0400
From:	"John Stoffel" <john@...ffel.org>
To:	Andrew Morton <akpm@...l.org>
Cc:	"John Stoffel" <john@...ffel.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.18-rc5-mm1, make oldconfig from 2.6.18-rc5 destroys LVM

>>>>> "Andrew" == Andrew Morton <akpm@...l.org> writes:

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

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

Well, maybe the hotfix patch converts all the uses of 'if BLOCK' to
'if CONFIG_BLOCK', but I still think that 'if USE_BLOCK_DEVS' would be
more clear.  It's not like it should be all *that* used outside of
config stuff.

Oh well, thanks for your reply, now I can test 2.6.18-rc5-mm1 and see
if my IRQ problem is really there or not.

John

-- 
VGER BF report: U 0.5
-
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/