Hi,

On Wed, Nov 8, 2023 at 12:40 PM Stefan Hajnoczi <stefa...@gmail.com> wrote:
>
> On Wed, 8 Nov 2023 at 19:05, Philippe Mathieu-Daudé <phi...@linaro.org> wrote:
> >
> > Hi Stefan,
> >
> > You are listed as virtiofs maintainer, see MAINTAINERS:
> >
> >    virtiofs
> >    M: Stefan Hajnoczi <stefa...@redhat.com>
> >    S: Supported
> >    F: hw/virtio/vhost-user-fs*
> >    F: include/hw/virtio/vhost-user-fs.h
> >    L: virtio...@redhat.com
> >
> > Mails sent to this list address are bouncing:
> >
> > <virtio...@redhat.com>: host int-mx-rdu2.corp.redhat.com[10.11.203.6]
> > said: 550
> >      5.1.1 <virtio...@redhat.com>: Recipient address rejected: User
> > unknown in
> >      local recipient table (in reply to RCPT TO command)
> >
> > Maybe the list need to be updated, like Daniel did with libvir-list@?
> > https://lore.kernel.org/qemu-devel/20231027095643.2842382-1-berra...@redhat.com/
>
> Yes, it does. The new mailing list address has not been created yet.
> I'll update the MAINTAINERS file when the new mailing list becomes
> available in the coming days.
>
> > Looking at other lists, I also see secalert@:
> >
> >    $ git grep L:.*redhat MAINTAINERS
> >    MAINTAINERS:86:L: secal...@redhat.com
> >    MAINTAINERS:2231:L: virtio...@redhat.com
> >
> > So Cc'ing Michael / Mauro.
>
> I'm not sure about secalert. Thanks for CCing Michael and Mauro.

secalert@ is regularly monitored and working fine. Perhaps we can add
qemu-secur...@nongnu.org, in addition to secalert, to match what's
stated in the 'Security Process' page.

```
diff --git a/MAINTAINERS b/MAINTAINERS
index 8e8a7d5be5..af74d5487f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -83,6 +83,7 @@ Responsible Disclosure, Reporting Security Issues
 -------------------------------------------------
 W: https://wiki.qemu.org/SecurityProcess
 M: Michael S. Tsirkin <m...@redhat.com>
+L: qemu-secur...@nongnu.org
 L: secal...@redhat.com

 Trivial patches
```

> Thanks,
> Stefan
>

Thank you,
-- 
Mauro Matteo Cascella
Red Hat Product Security
PGP-Key ID: BB3410B0


Reply via email to