From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: virtio-fs@redhat.com, stefanha@redhat.com, qemu-devel@nongnu.org,
amulmek1@in.ibm.com
Subject: Re: [PATCH] virtiofsd: Seccomp: Add 'send' for syslog
Date: Mon, 2 Nov 2020 15:13:50 +0000 [thread overview]
Message-ID: <20201102151350.GH3673@work-vm> (raw)
In-Reply-To: <e1a007ed-7a9f-38cd-4003-144d0e99dd6e@redhat.com>
* Philippe Mathieu-Daudé (philmd@redhat.com) wrote:
> On 11/2/20 4:07 PM, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > On ppc it looks like syslog ends up using 'send' rather than 'sendto'.
> >
> > Reference: https://github.com/kata-containers/kata-containers/issues/1050
> >
> > Reported-by: amulmek1@in.ibm.com
> > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > ---
> > tools/virtiofsd/passthrough_seccomp.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/tools/virtiofsd/passthrough_seccomp.c b/tools/virtiofsd/passthrough_seccomp.c
> > index eb9af8265f..672fb72a31 100644
> > --- a/tools/virtiofsd/passthrough_seccomp.c
> > +++ b/tools/virtiofsd/passthrough_seccomp.c
> > @@ -118,6 +118,7 @@ static const int syscall_whitelist[] = {
> >
> > /* Syscalls used when --syslog is enabled */
> > static const int syscall_whitelist_syslog[] = {
>
> Is it worth restricting the syscall to POWER?
>
> #if defined(__powerpc64__)
I don't think so, since it's legal for a libc to use either;
so any other libc or architecture could choose either to use.
Dave
> > + SCMP_SYS(send),
>
> #endif
>
> > SCMP_SYS(sendto),
> > };
> >
> >
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-11-02 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 15:07 [PATCH] virtiofsd: Seccomp: Add 'send' for syslog Dr. David Alan Gilbert (git)
2020-11-02 15:11 ` Philippe Mathieu-Daudé
2020-11-02 15:13 ` Dr. David Alan Gilbert [this message]
2020-11-02 15:18 ` Daniel P. Berrangé
2020-11-02 16:43 ` Stefan Hajnoczi
2020-11-02 15:17 ` Daniel P. Berrangé
2020-11-02 18:30 ` Dr. David Alan Gilbert
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=20201102151350.GH3673@work-vm \
--to=dgilbert@redhat.com \
--cc=amulmek1@in.ibm.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=virtio-fs@redhat.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 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).