From: Chuck Ebbert <cebbert@redhat.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org, stable@kernel.org,
stable-review@kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, alan@lxorguk.ukuu.org.uk,
"Theodore Ts'o" <tytso@mit.edu>
Subject: Re: [000/165] 2.6.32.17-rc1 -stable review
Date: Sun, 1 Aug 2010 02:19:19 -0400 [thread overview]
Message-ID: <20100801021919.1e8c2adb@katamari> (raw)
In-Reply-To: <20100730171550.GA1299@kroah.com>
On Fri, 30 Jul 2010 10:15:50 -0700
Greg KH <gregkh@suse.de> wrote:
>
> This is the start of the stable review cycle for the 2.6.32.17 release.
> There are 165 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let us know. If anyone is a maintainer of the proper subsystem, and
> wants to add a Signed-off-by: line to the patch, please respond with it.
>
> Responses should be made by August 1, 2010, 18:00:00 UTC.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> kernel.org/pub/linux/kernel/v2.6/stable-review/patch-2.6.32.17-rc1.gz
> and the diffstat can be found below.
>
I still don't see this one in 2.6.32-stable:
commit 1f5a81e41f8b1a782c68d3843e9ec1bfaadf7d72 upstream.
Subject: ext4: Make sure the MOVE_EXT ioctl can't overwrite append-only files
This fixes CVE-2010-2066; I'm pretty sure 2.6.32 is vulnerable.
next prev parent reply other threads:[~2010-08-01 6:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 17:15 [000/165] 2.6.32.17-rc1 -stable review Greg KH
2010-08-01 6:19 ` Chuck Ebbert [this message]
2010-08-02 17:05 ` Greg KH
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=20100801021919.1e8c2adb@katamari \
--to=cebbert@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable-review@kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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.