From: "Daniel P. Berrangé" <berrange@redhat.com>
To: otubo@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 0/5] seccomp: fix hole in blocking forks
Date: Mon, 31 Jan 2022 09:09:24 +0000 [thread overview]
Message-ID: <YfenRCFq//iHpLKI@redhat.com> (raw)
In-Reply-To: <CAGMDDkfCM5bvyTDm02tNnu3Z6cS_0OZWST-FA5qGGJPDBgeprQ@mail.gmail.com>
On Mon, Jan 31, 2022 at 10:07:43AM +0100, Eduardo Otubo wrote:
> On Fri, Jan 28, 2022 at 4:42 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > Hi Eduardo,
> >
> > You acked this series, but going through my old git branches I
> > just discovered that this never got merged. I guess I was assuming
> > you had queued it for a future PULL when you acked it.
> >
> > I don't mind sending a pull request myself if you've no objections.
>
> I don't mind at all. Thanks for letting me know! I might have missed it somehow.
Ok, I'll send it, since I have some other unrelated stuff needing sending
too.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2022-01-31 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 13:02 [PATCH 0/5] seccomp: fix hole in blocking forks Daniel P. Berrangé
2021-08-02 13:02 ` [PATCH 1/5] seccomp: allow action to be customized per syscall Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 2/5] seccomp: add unit test for seccomp filtering Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 3/5] seccomp: fix blocking of process spawning Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 4/5] seccomp: block use of clone3 syscall Daniel P. Berrangé
2021-08-02 13:03 ` [PATCH 5/5] seccomp: block setns, unshare and execveat syscalls Daniel P. Berrangé
2021-08-04 8:05 ` [PATCH 0/5] seccomp: fix hole in blocking forks Eduardo Terrell Ferrari Otubo
2022-01-28 15:42 ` Daniel P. Berrangé
2022-01-31 9:07 ` Eduardo Otubo
2022-01-31 9:09 ` Daniel P. Berrangé [this message]
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=YfenRCFq//iHpLKI@redhat.com \
--to=berrange@redhat.com \
--cc=otubo@redhat.com \
--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 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.