From: Greg KH <greg@kroah.com>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
torvalds@osdl.org, stable@kernel.org
Subject: Re: Linux 2.6.18.7
Date: Tue, 20 Feb 2007 14:46:14 -0800 [thread overview]
Message-ID: <20070220224614.GA4390@kroah.com> (raw)
In-Reply-To: <45DB688F.1070209@redhat.com>
On Tue, Feb 20, 2007 at 04:30:55PM -0500, Chuck Ebbert wrote:
> Greg KH wrote:
> > We (the -stable team) are announcing the release of the 2.6.18.7 kernel.
> > It contains one NFS fix that if you run a NFS server, you might want to
> > apply.
>
> Well that's nice. There's at least one other unfixed CVE
> in 2.6.18.6 -- why didn't you fix that? (The patch has been
> queued for two months now.)
I'm working on pushing the 2.6.18-stable queue out soon, sorry, been
backed up with other things recently.
I pushed this one out so quickly, as it was able to be triggered
remotely, unlike the current patches in the 2.6.18-stable queue.
thanks,
greg k-h
prev parent reply other threads:[~2007-02-20 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-20 6:59 Greg KH
2007-02-20 7:05 ` Greg KH
2007-02-20 21:30 ` Chuck Ebbert
2007-02-20 22:46 ` Greg KH [this message]
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=20070220224614.GA4390@kroah.com \
--to=greg@kroah.com \
--cc=akpm@osdl.org \
--cc=cebbert@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome