From: Greg KH <gregkh@linuxfoundation.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, Will Drewry <wad@chromium.org>,
Kees Cook <keescook@chromium.org>,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH 3.5 0/2] seccomp and vsyscall fixes
Date: Thu, 27 Sep 2012 13:09:21 -0700 [thread overview]
Message-ID: <20120927200921.GA16868@kroah.com> (raw)
In-Reply-To: <CALCETrUi5RrJoq9CS8mA31tiT9WPW4cc27zyjymAj5uqWqMptw@mail.gmail.com>
On Thu, Sep 27, 2012 at 12:40:10PM -0700, Andy Lutomirski wrote:
> [cc James Morris]
>
> This has been pending since the 3.6 merge window. Patch 2/2 barely
> matters because it's almost impossible to detect its effect -- it's
> more about future proofing against new architectures. Patch 1/2 has
> been slightly tweaked here:
>
> http://lkml.kernel.org/r/%3C744e07394a02be3d3ef52c22ccedb24d9a478fe1.1343869850.git.luto@amacapital.net%3E
>
> and will soon appear here (once the cache refreshes)
>
> https://git.kernel.org/?p=linux/kernel/git/luto/linux.git;a=shortlog;h=refs/heads/seccomp-vsyscall/patch_v2
>
> I can wait for someone to pick it up or I can send a pull request from
> my tree. FWIW, the same patch applies cleanly to -next.
You might want to resend them, in patch form, to James, if he's missed
them already.
thanks,
greg k-h
prev parent reply other threads:[~2012-09-27 20:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 23:19 Andy Lutomirski
2012-07-17 23:19 ` [PATCH 3.5 1/2] seccomp: Make syscall skipping and nr changes more consistent Andy Lutomirski
2012-07-18 18:31 ` Will Drewry
2012-07-18 20:00 ` Andy Lutomirski
2012-07-26 15:43 ` Andy Lutomirski
2012-07-17 23:19 ` [PATCH 3.5 2/2] seccomp: Future-proof against silly tracers Andy Lutomirski
2012-07-18 2:13 ` Will Drewry
2012-07-18 18:35 ` Will Drewry
2012-07-18 20:08 ` Andy Lutomirski
2012-07-26 15:41 ` Andy Lutomirski
2012-08-02 14:32 ` Will Drewry
2012-08-02 16:54 ` Andy Lutomirski
2012-07-18 2:10 ` [PATCH 3.5 0/2] seccomp and vsyscall fixes Will Drewry
2012-09-27 17:36 ` Greg KH
2012-09-27 19:40 ` Andy Lutomirski
2012-09-27 20:09 ` Greg KH [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=20120927200921.GA16868@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jmorris@namei.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=torvalds@linux-foundation.org \
--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
Powered by JetHome