From: "Namsun Ch'o" <namnamc@Safe-mail.net>
To: eduardo.otubo@profitbricks.com
Cc: pmoore@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] Add argument filters to the seccomp sandbox
Date: Sun, 4 Oct 2015 00:15:47 -0400 [thread overview]
Message-ID: <N1-KgJlMJg0DI@Safe-mail.net> (raw)
> The pull request will be delayed a little bit due to some new patches
> incoming. Let's just set an agreement on how to approach regarding the
> "-runas and -chroot" patch and will prepare just a single batch for pull
> reuqest to Peter.
I also noticed that I had made that patch over the chroot and setuid patch, so
it won't apply without patch's fuzzing enabled. So that's probably a good
idea.
If I have a patch of 436 lines (296 added, 25 removed) which adds argument
filters for 12 syscalls, should I submit it in a new thread as a whole, or
break it up into like 3 syscalls at a time?
next reply other threads:[~2015-10-04 4:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-04 4:15 Namsun Ch'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-30 8:40 [Qemu-devel] [PATCH v3] Add argument filters to the seccomp sandbox Namsun Ch'o
2015-09-30 8:45 ` Daniel P. Berrange
2015-09-25 4:50 Namsun Ch'o
2015-09-29 15:22 ` Eduardo Otubo
2015-10-02 14:14 ` Eduardo Otubo
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=N1-KgJlMJg0DI@Safe-mail.net \
--to=namnamc@safe-mail.net \
--cc=eduardo.otubo@profitbricks.com \
--cc=pmoore@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 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).