| 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
| ||
|
Message-ID: <20150208110354.GM3185@redhat.com> Date: Sun, 8 Feb 2015 12:03:54 +0100 From: "Michael S. Tsirkin" <mst@...hat.com> To: Rusty Russell <rusty@...tcorp.com.au> Cc: lkml <linux-kernel@...r.kernel.org> Subject: Re: [PATCH 4/5] virtio: Don't expose legacy config features when VIRTIO_CONFIG_NO_LEGACY defined. On Fri, Feb 06, 2015 at 03:36:55PM +1030, Rusty Russell wrote: > The VIRTIO_F_ANY_LAYOUT and VIRTIO_F_NOTIFY_ON_EMPTY features are pre-1.0 > only. > > Signed-off-by: Rusty Russell <rusty@...tcorp.com.au> Acked-by: Michael S. Tsirkin <mst@...hat.com> > --- > include/uapi/linux/virtio_config.h | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/include/uapi/linux/virtio_config.h b/include/uapi/linux/virtio_config.h > index a6d0cdeaacd4..c18264df9504 100644 > --- a/include/uapi/linux/virtio_config.h > +++ b/include/uapi/linux/virtio_config.h > @@ -49,12 +49,14 @@ > #define VIRTIO_TRANSPORT_F_START 28 > #define VIRTIO_TRANSPORT_F_END 33 > > +#ifndef VIRTIO_CONFIG_NO_LEGACY > /* Do we get callbacks when the ring is completely used, even if we've > * suppressed them? */ > #define VIRTIO_F_NOTIFY_ON_EMPTY 24 > > /* Can the device handle any descriptor layout? */ > #define VIRTIO_F_ANY_LAYOUT 27 > +#endif /* VIRTIO_CONFIG_NO_LEGACY */ > > /* v1.0 compliant. */ > #define VIRTIO_F_VERSION_1 32 > -- > 2.1.0 -- 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/
Powered by blists - more mailing lists