public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kees Cook <kees.cook@canonical.com>
To: Joe Perches <joe@perches.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Pekka Enberg <penberg@kernel.org>,
	linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	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 18:00:18 -0800	[thread overview]
Message-ID: <20101110020018.GH5876@outflux.net> (raw)
In-Reply-To: <1289351010.28590.81.camel@Joe-Laptop>

On Tue, Nov 09, 2010 at 05:03:30PM -0800, Joe Perches wrote:
> On Tue, 2010-11-09 at 16:54 -0800, Linus Torvalds wrote:
> > On Tue, Nov 9, 2010 at 3:48 PM, Kees Cook <kees.cook@canonical.com> wrote:
> > >> I don't quite see where you got the particular collection of people from.
> > > I used scripts/get_maintainer.pl
> > Hmm. I get totally different results. You had
> >   linux-kernel@vger.kernel.org
> >   Al Viro <viro@zeniv.linux.org.uk>,
> >   Andrew Morton <akpm@linux-foundation.org>,
> >   Jiri Slaby <jslaby@suse.cz>,
> >   "David S. Miller" <davem@davemloft.net>
> > and I get
> >   Al Viro <viro@ZenIV.linux.org.uk>
> >   Andrew Morton <akpm@linux-foundation.org>
> >   Helge Deller <deller@gmx.de>
> >   David Howells <dhowells@redhat.com>
> >   Hugh Dickins <hughd@google.com>
> >   linux-kernel@vger.kernel.org
> > so there is something odd going on there.
> 
> I'd like to know as well.

Well, let's see what happens. If I rewind the tree to roughly
542181d3769d001c59cd17573dd4381e87d215f2 taking a wild guess at where my
tree was when I send the patch, and run it, here's what I get:

$ ./scripts/get_maintainer.pl 0001-ipc-initialize-structure-memory-to-zero-in-shm.patch
Al Viro <viro@zeniv.linux.org.uk>
Andrew Morton <akpm@linux-foundation.org>
Jiri Slaby <jslaby@suse.cz>
"Serge E. Hallyn" <serue@us.ibm.com>
"David S. Miller" <davem@davemloft.net>
linux-kernel@vger.kernel.org

And since I know Serge's address isn't at ibm any more, I dropped it from
Cc, assuming he didn't care about ipc structure fixups.

If I fast-forward to today and run it, I get the same output you do.

-Kees

-- 
Kees Cook
Ubuntu Security Team

  reply	other threads:[~2010-11-10  2:00 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
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 [this message]
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=20101110020018.GH5876@outflux.net \
    --to=kees.cook@canonical.com \
    --cc=akpm@linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=hughd@google.com \
    --cc=joe@perches.com \
    --cc=jslaby@suse.cz \
    --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