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
| ||
|
Date: Mon, 17 Feb 2020 18:27:50 +0100 From: Stefano Garzarella <sgarzare@...hat.com> To: Jorgen Hansen <jhansen@...are.com> Cc: "mtk.manpages@...il.com" <mtk.manpages@...il.com>, "linux-man@...r.kernel.org" <linux-man@...r.kernel.org>, Stefan Hajnoczi <stefanha@...hat.com>, Dexuan Cui <decui@...rosoft.com>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> Subject: Re: [PATCH v2] vsock.7: add VMADDR_CID_LOCAL description On Mon, Feb 17, 2020 at 01:55:58PM +0000, Jorgen Hansen wrote: > > From: Stefano Garzarella [mailto:sgarzare@...hat.com] > > Sent: Friday, February 14, 2020 2:08 PM > > To: mtk.manpages@...il.com > > Cc: Jorgen Hansen <jhansen@...are.com>; linux-man@...r.kernel.org; > > Stefan Hajnoczi <stefanha@...hat.com>; Dexuan Cui > > <decui@...rosoft.com>; netdev@...r.kernel.org > > Subject: [PATCH v2] vsock.7: add VMADDR_CID_LOCAL description > > > > Linux 5.6 added the new well-known VMADDR_CID_LOCAL for local > > communication. > > > > This patch explains how to use it and remove the legacy > > VMADDR_CID_RESERVED no longer available. > > > > Signed-off-by: Stefano Garzarella <sgarzare@...hat.com> > > --- > > v2: > > * rephrased "Local communication" description [Stefan] > > * added a mention of previous versions that supported > > loopback only in the guest [Stefan] > > --- > > > > @@ -222,6 +232,11 @@ are valid. > > Support for VMware (VMCI) has been available since Linux 3.9. > > KVM (virtio) is supported since Linux 4.8. > > Hyper-V is supported since Linux 4.14. > > +.PP > > +VMADDR_CID_LOCAL is supported since Linux 5.6. > > +Local communication in the guest and on the host is available since Linux > > 5.6. > > +Previous versions partially supported it only in the guest and only > > +with some transports (VMCI and virtio). > > Maybe rephrase the last part slightly to something like: > > Previous versions only supported local communication within a guest (not on the host), > and only with some transports (VMCI and virtio). I think it is better, I'll send a v3 with this part changed :-) > > Otherwise, looks good to me. Thanks for making this update. > > Reviewed-by: Jorgen Hansen <jhansen@...are.com> > Thanks, Stefano
Powered by blists - more mailing lists