From: Dave Chinner <david@fromorbit.com>
To: Sean Thomas Caron <scaron@umich.edu>
Cc: xfs@oss.sgi.com
Subject: Re: Safe to use XFS in production in Linux 3.2.9?
Date: Fri, 9 Mar 2012 10:53:26 +1100 [thread overview]
Message-ID: <20120308235326.GQ5091@dastard> (raw)
In-Reply-To: <20120308140600.77406b8zzy2zggkc@web.mail.umich.edu>
On Thu, Mar 08, 2012 at 02:06:00PM -0500, Sean Thomas Caron 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.
Hasn't it been fixed in 3.0.23? root exploits are the sort of thing
that are supposed to be fixed in long term stable kernels....
> I see that the newest recommended stable kernel on kernel.org is
> 3.2.9. Have there been any major changes to XFS between 3.0.12 and
> 3.2.9 that would be considered "risky" in a production environment?
The 3.2.x kernels really haven't been run in production environments
for that long for us to be able to tell if there are problems or
not.
> I assume the xfs-bulletproof-sync patch has already been committed
> to the code base in 3.2-train, so we shouldn't have to worry about
> that any longer?
Should have been, but I'm not exactly sure what is in that patch
Christoph gave you, so you'll have to verify that yourself.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-08 23:53 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 [this message]
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
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=20120308235326.GQ5091@dastard \
--to=david@fromorbit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox