public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Kees Cook <kees.cook@canonical.com>,
	Pekka Enberg <penberg@kernel.org>,
	linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
	Jiri Slaby <jslaby@suse.cz>,
	"David S. Miller" <davem@davemloft.net>,
	Hugh Dickins <hughd@google.com>,
	Manfred Spraul <manfred@colorfullife.com>
Subject: Re: [PATCH] ipc: explicitly clear stack memory in user structs
Date: Tue, 9 Nov 2010 15:09:06 -0800	[thread overview]
Message-ID: <20101109150906.af2804ac.akpm@linux-foundation.org> (raw)
In-Reply-To: <AANLkTint3yM44CouOvG_oA2K=_iC9AJuw-sJoB_HTUMT@mail.gmail.com>

On Tue, 9 Nov 2010 14:46:30 -0800
Linus Torvalds <torvalds@linux-foundation.org> wrote:

> On Tue, Nov 9, 2010 at 12:50 PM, Kees Cook <kees.cook@canonical.com> wrote:
> >
> > No one has committed it. I don't know why; I've sent it a few times now.
> 
> You seem to have sent it just to lkml. At least in this case the patch
> itself was not sent to me (only the subsequent replies were), and the
> choice of recipients was fairly odd apart from Andrew (who probably
> _is_ the right person).

It's in my backlog queue.  Waaaay back.  

The -rc1 merging and kermel summit put me way behind (again) and when
I'm way behind, I start to work in reverse order (mainly to avoid
looking at older versions of patches).  And when I'm working in
time-reverse order, things which were sent a long time ago get delayed
even more.

The good news is that the longer I take to merge something, the less
likely it is that I'll actually merge it ;) Either it got shot down or
a new version came out or someone else merged it.


  reply	other threads:[~2010-11-09 23:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-25 23:58 [PATCH] ipc: explicitly clear stack memory in user structs Kees Cook
2010-11-09 20:43 ` Pekka Enberg
2010-11-09 20:50   ` Kees Cook
2010-11-09 20:51     ` Pekka Enberg
2010-11-09 21:34       ` Pekka Enberg
2010-11-09 21:49         ` Kees Cook
2010-11-09 22:46     ` Linus Torvalds
2010-11-09 23:09       ` Andrew Morton [this message]
2010-11-09 23:48       ` Kees Cook
2010-11-10  0:54         ` Linus Torvalds
2010-11-10  1:03           ` Joe Perches
2010-11-10  2:00             ` Kees Cook
2010-11-11  7:37               ` Pekka Enberg

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=20101109150906.af2804ac.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=hughd@google.com \
    --cc=jslaby@suse.cz \
    --cc=kees.cook@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=penberg@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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