From: Eric Sandeen <sandeen@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: stable@kernel.org, ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [stable] [PATCH] stable - ext[234]: Avoid printk floods in the face of directory corruption (CVE-2008-3528)
Date: Wed, 22 Oct 2008 14:33:55 -0500 [thread overview]
Message-ID: <48FF8023.4010108@redhat.com> (raw)
In-Reply-To: <20081022173752.GA10587@kroah.com>
Greg KH wrote:
> Yes, the fun "physical access" issue, right?
>
> But for some, who run Linux in a "kiosk" mode, or in semi-secured places
> like university labs, something like this would matter, so you might
> want to notify the distros of this issue through vendor-sec and let them
> make up their minds if they wish to backport the fixes to their
> supported releases.
Well, the CVE should do that, right... distro security teams should be
looking at the CVEs.
-Eric
next prev parent reply other threads:[~2008-10-22 19:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 15:11 [PATCH] stable - ext[234]: Avoid printk floods in the face of directory corruption (CVE-2008-3528) Eric Sandeen
2008-10-22 16:14 ` [stable] " Greg KH
2008-10-22 16:21 ` Eric Sandeen
2008-10-22 16:34 ` Greg KH
2008-10-22 17:35 ` Eric Sandeen
2008-10-22 17:37 ` Greg KH
2008-10-22 19:33 ` Eric Sandeen [this message]
2008-10-23 20:52 ` patch ext-avoid-printk-floods-in-the-face-of-directory-corruption.patch added to 2.6.27-stable tree gregkh
2008-10-23 21:04 ` patch ext-avoid-printk-floods-in-the-face-of-directory-corruption.patch added to 2.6.25-stable tree gregkh
2008-10-23 21:12 ` patch ext-avoid-printk-floods-in-the-face-of-directory-corruption.patch added to 2.6.26-stable tree gregkh
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=48FF8023.4010108@redhat.com \
--to=sandeen@redhat.com \
--cc=greg@kroah.com \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@kernel.org \
/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.