From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45916) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZiaiC-0001Gb-Uz for qemu-devel@nongnu.org; Sun, 04 Oct 2015 00:15:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ziai9-00078u-PD for qemu-devel@nongnu.org; Sun, 04 Oct 2015 00:15:48 -0400 Received: from www.safe-mail.net ([212.29.227.230]:51385 helo=tapuz.safe-mail.net) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ziai9-00078p-GS for qemu-devel@nongnu.org; Sun, 04 Oct 2015 00:15:45 -0400 Date: Sun, 4 Oct 2015 00:15:47 -0400 From: "Namsun Ch'o" Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3] Add argument filters to the seccomp sandbox List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: eduardo.otubo@profitbricks.com Cc: pmoore@redhat.com, qemu-devel@nongnu.org > 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?