From: Martin Steigerwald <Martin@lichtvoll.de>
To: xfs@oss.sgi.com
Cc: Sean Thomas Caron <scaron@umich.edu>,
Greg Freemyer <greg.freemyer@gmail.com>
Subject: Re: Safe to use XFS in production in Linux 3.2.9?
Date: Sun, 11 Mar 2012 12:33:18 +0100 [thread overview]
Message-ID: <201203111233.18986.Martin@lichtvoll.de> (raw)
In-Reply-To: <CAGpXXZLQp+m_soTBw8Zq-M0cyKqVTASSAXMt6YV07ntfqJhMag@mail.gmail.com>
Am Freitag, 9. März 2012 schrieb Greg Freemyer:
> On Thu, Mar 8, 2012 at 2:06 PM, Sean Thomas Caron <scaron@umich.edu>
wrote:
> > Hi all,
> >
> > We're currently using Linux 3.0.12 with Cristoph's
> > xfs-bulletproof-sync patch and it seems to be working very well for
> > us. Unfortunately this kernel is vulnerable to the recent
> > CVE-2012-0056 no permission checking on writes to /proc/(pid)/mem
> > local root exploit, so we've got to leave it behind.
> >
> > I see that the newest recommended stable kernel on kernel.org is
> > 3.2.9.
>
> Sean,
>
> You do appreciate 3.0 has been designated a long-term kernel by the
> kernel.org team and will get kernel.org support for 2 years. 3.2 is
> not a long-term kernel, so support drops from kernel.org more or less
> when 3.3 comes out.
>
> 3.2 support will come from the distributors of course, but I don't know
> if any of the major releases are based on 3.2.
AFAIR Ubuntu 12.04 as well as Debian Wheezy will use kernel 3.2.
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-03-11 11:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 19:06 Safe to use XFS in production in Linux 3.2.9? Sean Thomas Caron
2012-03-08 23:53 ` Dave Chinner
2012-03-09 16:08 ` Sean Thomas Caron
2012-03-09 16:45 ` Ben Myers
2012-03-09 16:56 ` Sean Thomas Caron
2012-03-09 16:50 ` Greg Freemyer
2012-03-09 16:55 ` Sean Thomas Caron
2012-03-11 11:33 ` Martin Steigerwald [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=201203111233.18986.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=greg.freemyer@gmail.com \
--cc=scaron@umich.edu \
--cc=xfs@oss.sgi.com \
/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.