From: Stefano Garzarella <sgarzare@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Jason Wang" <jasowang@redhat.com>,
"Eugenio Pérez" <eperezma@redhat.com>
Subject: Re: vhost-vdpa potential fd leak (coverity issue)
Date: Mon, 14 Jul 2025 12:33:00 +0200 [thread overview]
Message-ID: <CAGxU2F7ndXZN0Kzadk8doCV-9s_FyHhxkoH_rpyD7XQzLs=Cdw@mail.gmail.com> (raw)
In-Reply-To: <CAFEAcA-jqjuC+a7AH1wgde8=y_yTc_iE-MriwzT+RZMP7U070Q@mail.gmail.com>
On Mon, 14 Jul 2025 at 11:51, Peter Maydell <peter.maydell@linaro.org> wrote:
>
> On Mon, 14 Jul 2025 at 10:19, Stefano Garzarella <sgarzare@redhat.com> wrote:
> > On Thu, Jul 10, 2025 at 12:40:43PM -0400, Michael S. Tsirkin wrote:
> > >> Q: should this file be listed in the "vhost" subcategory of
> > >> MAINTAINERS?
> > >> At the moment it only gets caught by "Network device backends".
> >
> > Maybe yes, but it's really virtio-net specific.
> > @Michael WDYT?
>
> You could create a new virtio-net subsection if that works
> better (and we could move the two virtio-net* files
> currently listed under "Network devices" into it).
> The aim here should really be to ensure that the people
> interested in reviewing/queueing patches get cc'd.
Just added net/vhost* filese under vhost section:
https://lore.kernel.org/qemu-devel/20250714102626.34431-1-sgarzare@redhat.com/T/#u
Not sure about virtio-net subsection, I'm not really involved, so I'd
leave to someone else.
Thanks,
Stefano
next prev parent reply other threads:[~2025-07-14 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 15:46 vhost-vdpa potential fd leak (coverity issue) Peter Maydell
2025-07-10 16:40 ` Michael S. Tsirkin
2025-07-14 9:18 ` Stefano Garzarella
2025-07-14 9:48 ` Peter Maydell
2025-07-14 10:33 ` Stefano Garzarella [this message]
2025-07-14 9:57 ` Michael S. Tsirkin
2025-07-14 10:20 ` Stefano Garzarella
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='CAGxU2F7ndXZN0Kzadk8doCV-9s_FyHhxkoH_rpyD7XQzLs=Cdw@mail.gmail.com' \
--to=sgarzare@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).