From: Linus Torvalds <torvalds@linux-foundation.org>
To: Eric Paris <eparis@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Greg KH <gregkh@linuxfoundation.org>,
linux-audit@redhat.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking
Date: Tue, 10 Jun 2014 08:48:37 -0700 [thread overview]
Message-ID: <CA+55aFweMYR_8TFsfUNc0JxpNas06asUC-BvWi_T-XrhBtrtuw@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFxzrJ6vBEJcByUO2+auO7k8AMJPTYH8t9K0xx=uxoqPOQ@mail.gmail.com>
On Tue, Jun 10, 2014 at 8:42 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> Ok, I'll take your patch-series rather than the recent pull from Andy,
> and pick up #2 that way too.
Hmm. In fact, #2 doesn't apply cleanly. It's trivial to fix up, but
rather than do that, the reject made me go "I'll just forward this to
Peter Anvin" instead, so that he's aware of the x32 issue.
Linus
next prev parent reply other threads:[~2014-06-10 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 3:09 [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking Eric Paris
2014-06-09 22:30 ` Greg KH
2014-06-09 22:35 ` Andy Lutomirski
2014-06-09 22:46 ` Greg KH
2014-06-09 22:55 ` Andy Lutomirski
2014-06-10 0:32 ` Greg KH
2014-06-10 0:30 ` Andy Lutomirski
2014-06-10 0:37 ` Greg KH
2014-06-09 23:35 ` Josh Boyer
2014-06-10 0:31 ` Greg KH
2014-06-09 22:53 ` Linus Torvalds
2014-06-09 22:56 ` Andy Lutomirski
2014-06-09 23:36 ` Linus Torvalds
2014-06-10 12:50 ` Eric Paris
2014-06-10 15:42 ` Linus Torvalds
2014-06-10 15:48 ` Linus Torvalds [this message]
[not found] <cover.1401315521.git.luto@amacapital.net>
2014-05-28 22:21 ` Andy Lutomirski
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=CA+55aFweMYR_8TFsfUNc0JxpNas06asUC-BvWi_T-XrhBtrtuw@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=stable@vger.kernel.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).