From: Andy Lutomirski <luto@amacapital.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
Eric Paris <eparis@redhat.com>,
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: Mon, 9 Jun 2014 15:56:58 -0700 [thread overview]
Message-ID: <CALCETrXBSd4qKJE+yVp0YTPdrCDSfGf_SOxaZFgQpULg1bF3aA@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwmajRnDOiBmZQf8rpVE-HigsDYy9oy-TsWLzn-vdyF+Q@mail.gmail.com>
On Mon, Jun 9, 2014 at 3:53 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Mon, Jun 9, 2014 at 3:35 PM, Andy Lutomirski <luto@amacapital.net> wrote:
>>
>> Hmm. It seems that it didn't make it into Linus' tree. Crap.
>
> I assume that if there is a maintainer who normally sends me stuff by
> git, when I see patches in emails they are just informational
> heads-ups about stuff that is being discussed or pending, and that
> I'll see it later in a pull request. So I just ignore them unless I
> have specific comments, since clearly the emailed patch is just
> informational and/or for comments/acks from others.
>
> The exception is unless it *VERY CLEARLY* says otherwise (as in
> "Linus, can you please take this directly due to xyz").
>
> Because why would somebody send me a patch series sometimes, and git
> trees at other times? That would just be stupid.
In this particular case, it's my patch, and I've never sent you a pull
request. I sort of assumed that security@kernel.org magically caused
acknowledged fixes to end up in your tree. I'm not sure what I'm
supposed to do here.
Maybe the confusion is because Eric resent the patch?
--Andy
next prev parent reply other threads:[~2014-06-09 22:57 UTC|newest]
Thread overview: 23+ 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-05-29 3:09 ` [PATCH 2/2] audit: do not select HAVE_ARCH_AUDITSYSCALL on x32 Eric Paris
2014-06-09 22:30 ` [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking 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-10 0:51 ` Andy Lutomirski
2014-06-10 2:57 ` Greg KH
2014-06-10 4:04 ` Andy Lutomirski
2014-06-10 4:14 ` Greg KH
2014-06-09 22:53 ` Linus Torvalds
2014-06-09 22:56 ` Andy Lutomirski [this message]
2014-06-09 23:36 ` Linus Torvalds
2014-06-10 12:50 ` Eric Paris
2014-06-10 12:50 ` Eric Paris
2014-06-10 15:42 ` Linus Torvalds
2014-06-10 15:48 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2014-05-28 22:21 [PATCH 0/2] Fix auditsc DoS and move it to staging Andy Lutomirski
2014-05-28 22:21 ` [PATCH 1/2] auditsc: audit_krule mask accesses need bounds checking 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=CALCETrXBSd4qKJE+yVp0YTPdrCDSfGf_SOxaZFgQpULg1bF3aA@mail.gmail.com \
--to=luto@amacapital.net \
--cc=eparis@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.