linux-kernel - Re: [PATCH] virtio_blk: add block topology support

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]

Date:	Mon, 01 Aug 2011 14:52:10 +0930
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Christoph Hellwig <hch@....de>
Cc:	Alexey Zaytsev <alexey.zaytsev@...il.com>,
	Christoph Hellwig <hch@....de>,
	Christian Borntraeger <borntraeger@...ibm.com>,
	Avishay Traeger <avishay@...ibm.com>,
	linux-kernel@...r.kernel.org, Avi Kivity <avi@...hat.com>
Subject: Re: [PATCH] virtio_blk: add block topology support

On Sun, 31 Jul 2011 20:19:05 +0200, Christoph Hellwig <hch@....de> wrote:
> On Sat, Jul 30, 2011 at 02:22:42PM +0930, Rusty Russell wrote:
> > > I guess you could just remove VIRTIO_BLK_F_SECTOR_MAX from the spec.
> > > Linux did not implement it, and virtualbox does not have virtio block
> > > support at all. Are there any other known users, who might have
> > > implemented the  VIRTIO_BLK_F_SECTOR_MAX feature?
> > 
> > Did qemu implement it?  If not, we'll simply kill it, and pretend it
> > never happened...
> 
> It was never added to either qemu or the kernel.  It would really help
> if we had a copy of the spec in a readable format (that is plain text)
> in major implementations of virtio like qemu and the kernel.

That's a really good idea.  I've prepared a patch which puts the latest
version in the kernel source (Documentation/virtio/virtio-spec.txt).

Thanks!
Rusty.

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