public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Paul Moore <pmoore@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org, jmorris@namei.org,
	wad@chromium.org, otubo@linux.vnet.ibm.com
Subject: Re: [PATCH v2 1/3] seccomp: Add SECCOMP_RET_INFO return value
Date: Mon, 14 Jan 2013 16:50:27 -0500	[thread overview]
Message-ID: <50F47DA3.8000103@linux.vnet.ibm.com> (raw)
In-Reply-To: <4315919.Nu3gOqZ3yQ@sifl>



On 01/14/2013 04:45 PM, Paul Moore wrote:
> On Monday, January 07, 2013 12:09:03 PM Corey Bryant wrote:
>> Adds a new return value to seccomp filters that causes an
>> informational kernel message to be printed.  The message
>> includes the system call number and architecture.
>>
>> This can be used to learn the system calls that a process
>> is using.
>>
>> Signed-off-by: Corey Bryant <coreyb@linux.vnet.ibm.com>
>
> Were do things currently stand with this patchset?  It still seems like a
> reasonable addition to me.
>

Thanks for asking.  I haven't heard anything in response to the v2 
patches.  Does anyone have any comments/thoughts?

-- 
Regards,
Corey Bryant


      reply	other threads:[~2013-01-14 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 17:09 [PATCH v2 1/3] seccomp: Add SECCOMP_RET_INFO return value Corey Bryant
2013-01-07 17:09 ` [PATCH v2 2/3] Documentation: " Corey Bryant
2013-01-07 17:09 ` [PATCH v2 3/3] samples: Add sample using SECCOMP_RET_INFO Corey Bryant
2013-01-14 21:45 ` [PATCH v2 1/3] seccomp: Add SECCOMP_RET_INFO return value Paul Moore
2013-01-14 21:50   ` Corey Bryant [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=50F47DA3.8000103@linux.vnet.ibm.com \
    --to=coreyb@linux.vnet.ibm.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=otubo@linux.vnet.ibm.com \
    --cc=pmoore@redhat.com \
    --cc=wad@chromium.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