From: Jakub Kicinski <kuba@kernel.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
xieyongji@bytedance.com, jasowang@redhat.com,
david.marchand@redhat.com, lulu@redhat.com,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, xuanzhuo@linux.alibaba.com,
eperezma@redhat.com
Subject: Re: [PATCH v3 0/3] vduse: add support for networking devices
Date: Thu, 10 Aug 2023 14:29:49 -0700 [thread overview]
Message-ID: <20230810142949.074c9430@kernel.org> (raw)
In-Reply-To: <20230810150347-mutt-send-email-mst@kernel.org>
On Thu, 10 Aug 2023 15:04:27 -0400 Michael S. Tsirkin wrote:
> Another question is that with this userspace can inject
> packets directly into net stack. Should we check CAP_NET_ADMIN
> or such?
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.
Or you mean directly into the network?
next prev parent reply other threads:[~2023-08-10 21:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 10:04 [PATCH v3 0/3] vduse: add support for networking devices Maxime Coquelin
2023-07-05 10:04 ` Maxime Coquelin
2023-07-05 10:04 ` [PATCH v3 1/3] vduse: validate block features only with block devices Maxime Coquelin
2023-07-05 10:04 ` Maxime Coquelin
2023-07-05 10:04 ` [PATCH v3 2/3] vduse: enable Virtio-net device type Maxime Coquelin
2023-07-05 10:04 ` Maxime Coquelin
2023-07-05 10:04 ` [PATCH v3 3/3] vduse: Temporarily disable control queue features Maxime Coquelin
2023-07-05 10:04 ` Maxime Coquelin
2023-07-06 1:58 ` Jason Wang
2023-07-06 1:58 ` Jason Wang
2023-08-10 19:04 ` [PATCH v3 0/3] vduse: add support for networking devices Michael S. Tsirkin
2023-08-10 19:04 ` Michael S. Tsirkin
2023-08-10 21:29 ` Jakub Kicinski [this message]
2023-08-10 21:42 ` Michael S. Tsirkin
2023-08-10 21:42 ` Michael S. Tsirkin
2023-08-10 22:00 ` Jakub Kicinski
2023-08-29 13:34 ` Maxime Coquelin
2023-08-29 13:34 ` Maxime Coquelin
2023-08-29 17:05 ` Michael S. Tsirkin
2023-08-29 17:05 ` Michael S. Tsirkin
2023-08-30 11:27 ` Maxime Coquelin
2023-08-30 11:27 ` Maxime Coquelin
2023-08-30 13:30 ` Michael S. Tsirkin
2023-08-30 13:30 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230810142949.074c9430@kernel.org \
--to=kuba@kernel.org \
--cc=david.marchand@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=xieyongji@bytedance.com \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.