|From:||Will Drewry <wad-AT-chromium.org>|
|To:||James Morris <jmorris-AT-namei.org>|
|Subject:||Re: [PATCH v9 05/13] seccomp_filter: Document what seccomp_filter is and how it works.|
|Date:||Wed, 29 Jun 2011 14:13:09 -0500|
|Cc:||Chris Evans <scarybeasts-AT-gmail.com>, linux-kernel-AT-vger.kernel.org, torvalds-AT-linux-foundation.org, djm-AT-mindrot.org, segoon-AT-openwall.com, kees.cook-AT-canonical.com, mingo-AT-elte.hu, rostedt-AT-goodmis.org, fweisbec-AT-gmail.com, tglx-AT-linutronix.de, Randy Dunlap <rdunlap-AT-xenotime.net>, linux-doc-AT-vger.kernel.org, Eric Paris <eparis-AT-redhat.com>|
On Sun, Jun 26, 2011 at 6:20 PM, James Morris <email@example.com> wrote: > On Fri, 24 Jun 2011, Chris Evans wrote: > >> With patches like these, there can be the concern: will anyone actually use >> it?? > > It's likely to be used by kvm/qemu to help protect against vm break-outs. Since it seems that there'll be consumers (openssh, vsftpd, kvm/qemu, chromium, chromium os) and feedback quieted down, what are the next steps to get this to a pull/no-pull decision points (or at least some Ack's or Nack's)? I know this patch series crosses a number of maintainers, and I never know exactly what's next when the feedback slows down. Thanks! will -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Copyright © 2011, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds