lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 11 Feb 2008 00:00:43 -0800
From:	Daniel Phillips <phillips@...nq.net>
To:	"Pekka Enberg" <penberg@...helsinki.fi>
Cc:	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	stable@...nel.org, jens.axboe@...cle.com,
	akpm@...ux-foundation.org, bastian@...di.eu.org, ndenev@...il.com,
	oliver.pntr@...il.com
Subject: Re: [PATCH] vmsplice exploit fix (was: splice: fix user pointer access in get_iovec_page_array)

On Sunday 10 February 2008 23:49, Pekka Enberg wrote:
> Hi Daniel,
>
> On Feb 11, 2008 9:29 AM, Daniel Phillips <phillips@...nq.net> wrote:
> > I think many users would first go to kernel.org 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 stable@...nel.org 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.

Regards,

Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ