linux-kernel - Re: Future of md multipath

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <E1Lg2pL-0003s6-4e@be1.7eggert.dyndns.org>
Date:	Sat, 07 Mar 2009 21:08:54 +0100
From:	Bodo Eggert <7eggert@....de>
To:	martin f krafft <madduck@...ian.org>, Neil Brown <neilb@...e.de>,
	Christoph Hellwig <hch@....de>, linux-raid@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: Future of md multipath

martin f krafft <madduck@...ian.org> wrote:
> also sprach Neil Brown <neilb@...e.de> [2009.03.05.0349 +0100]:

>> I'm in favour of deprecating it.  Whenever I hear of people using it I
>> suggest dm-multipath, but there could people I don't here about.
>> I think the upcoming mdadm-3.0 will need a compile-time option to
>> enable multipath, so people will only get it if they really really
>> want it.
> 
> How do you propose a distro to deal with this? Keep it enabled for
> a certain time (with a deprecation warning?) and then just to close
> the doors on users who still need it?

What about reverting the patch for their kernels until they release the
next major version, then drop it?

For users who compile their kernels, add "Deprecated" to the description,
and rename the CONFIG_.

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