linux-kernel - Re: [PATCH] xen-blkfront: properly name all devices

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: <alpine.DEB.2.00.1204101710010.15151@kaball-desktop>
Date:	Tue, 10 Apr 2012 17:16:01 +0100
From:	Stefano Stabellini <stefano.stabellini@...citrix.com>
To:	Jan Beulich <JBeulich@...e.com>
CC:	Stefano Stabellini <Stefano.Stabellini@...citrix.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Jens Axboe <axboe@...nel.dk>,
	xen-devel <xen-devel@...ts.xen.org>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] xen-blkfront: properly name all devices

On Tue, 10 Apr 2012, Jan Beulich wrote:
> >>> On 10.04.12 at 17:50, Stefano Stabellini <stefano.stabellini@...citrix.com>
> > Would you be up for writing a couple of lines under Documentation to
> > clearly state what device names are going to be given by blkfront in
> > correspondence to vdev numbers?
> 
> I'm not really eager to, and in order to be useful, this should imo include
> the compat mapping, and specifically for this I'd prefer someone (you?)
> who was involved in putting this together to do eventual write-ups for it.
 
What compat mappings?
Do you mean the non-extended vdev names?

If you refer to the behavior of older kernels, I don't think it matters
here: the document is supposed to specify what the corresponding kernel
codebase does about xen block names, not what past kernels used to do.
Also, the Xen side vdev policy doesn't matter that much, because we
already clarified that it is up to the guest to choose whatever name it
wants for a given vdev.

In any case if you don't feel like writing it up, I'll do it.
--
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/