LKML Archive on
help / color / mirror / Atom feed
From: Daniel Phillips <>
To: "Pekka Enberg" <>
Subject: Re: [PATCH] vmsplice exploit fix (was: splice: fix user pointer access in get_iovec_page_array)
Date: Mon, 11 Feb 2008 00:00:43 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Sunday 10 February 2008 23:49, Pekka Enberg wrote:
> Hi Daniel,
> On Feb 11, 2008 9:29 AM, Daniel Phillips <> wrote:
> > I think many users would first go to on a day like
> > today, as I did.  Nothing to see there.  We could do a way better
> > job of getting the word out.
> Any suggestions what I could have done better here?

You did your part flawlessly as far as I can see.  Really, your original 
subject line was accurate, and lkml should not be the place to go to 
find the patch, but it is.

> As soon as Linus 
> merged the patch, I sent it to and expected
> information to spread from there. I did also follow up on some vendor
> bugzillas (Debian, RHEL, Fedora) to make sure they were aware of the
> merged patch (they were).

And they are no doubt getting kernel revs out at this very moment, that 
part of the machine works great.  It is just the part about getting out 
information to users who want to patch their own kernels that could be 
done better.



  reply	other threads:[~2008-02-11  8:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-10 14:47 [PATCH] splice: fix user pointer access in get_iovec_page_array() Pekka J Enberg
2008-02-10 15:17 ` Bastian Blank
2008-02-10 15:31   ` Oliver Pinter
2008-02-10 23:37 ` Willy Tarreau
2008-02-11  6:24   ` Oliver Pinter
2008-02-11  7:29 ` [PATCH] vmsplice exploit fix (was: splice: fix user pointer access in get_iovec_page_array) Daniel Phillips
2008-02-11  7:49   ` Pekka Enberg
2008-02-11  8:00     ` Daniel Phillips [this message]
2008-02-11  7:53   ` [stable] " Greg KH
2008-02-11  8:05     ` Daniel Phillips

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] vmsplice exploit fix (was: splice: fix user pointer access in get_iovec_page_array)' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).