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: <20230810150054.7baf34b7@kernel.org> Date: Thu, 10 Aug 2023 15:00:54 -0700 From: Jakub Kicinski <kuba@...nel.org> To: "Michael S. Tsirkin" <mst@...hat.com> Cc: Maxime Coquelin <maxime.coquelin@...hat.com>, xieyongji@...edance.com, jasowang@...hat.com, david.marchand@...hat.com, lulu@...hat.com, linux-kernel@...r.kernel.org, virtualization@...ts.linux-foundation.org, netdev@...r.kernel.org, xuanzhuo@...ux.alibaba.com, eperezma@...hat.com Subject: Re: [PATCH v3 0/3] vduse: add support for networking devices On Thu, 10 Aug 2023 17:42:11 -0400 Michael S. Tsirkin wrote: > > Directly into the stack? I thought VDUSE is vDPA in user space, > > meaning to get to the kernel the packet has to first go thru > > a virtio-net instance. > > yes. is that a sufficient filter in your opinion? Yes, the ability to create the device feels stronger than CAP_NET_RAW, and a bit tangential to CAP_NET_ADMIN. But I don't have much practical experience with virt so no strong opinion, perhaps it does make sense for someone's deployment? Dunno..
Powered by blists - more mailing lists