linux-kernel - Re: [PATCH 4/7] aoe: make dynamic block minor numbers the default

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: <20121002141734.56ee52b3.akpm@linux-foundation.org>
Date:	Tue, 2 Oct 2012 14:17:34 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ed Cashin <ecashin@...aid.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 4/7] aoe: make dynamic block minor numbers the default

On Mon, 1 Oct 2012 19:05:15 -0700
Ed Cashin <ecashin@...aid.com> wrote:

> Because udev use is so widespread, making the old static mapping
> the default is too conservative, given the severe limitations it
> places on usable AoE addresses.  Storage virtualization and
> larger shelves have made the old limitations too confining.
> 
> These changes make the dynamic block device minor numbers the
> default, removing the limitations on usable AoE addresses.
> 
> The static arrangement is still available with aoe_dyndevs=0, and
> the aoe-stat tool from the userland aoetools package, the user
> space counterpart to the aoe driver, recognizes the case where
> there is a mismatch between the minor number in sysfs and the
> minor number in a special device file.

Oh.  There we are.

Again, what are the back-(in)compatibility issues which users might
encounter with this?

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