From: Dave Chinner <david@fromorbit.com>
To: stable@vger.kernel.org
Cc: Fanael Linithien <fanael4@gmail.com>, xfs@oss.sgi.com
Subject: XFS fixes needed in stable kernels
Date: Wed, 20 Aug 2014 10:16:23 +1000 [thread overview]
Message-ID: <20140820001623.GT20518@dastard> (raw)
Hi Stable Kernel Gurus!
The following XFs fixes need to be pushed back to stable kernels.
The commits weren't all tagged in the recent 3.17-rc1 merge, so
you're getting an email from me instead. The commits required
from 3.17-rc1 are:
67dc288 xfs: ensure verifiers are attached to recovered buffers
5fd364f xfs: quotacheck leaves dquot buffers without verifiers
ad3714b xfs: dquot recovery needs verifiers
These are definitely needed for 3.16.y and 3.15.y, but aren't
critical for 3.14 and 3.13 because it only affects configurations
marked "experimetal: use at your own risk" and probably won't apply
easily. They aren't necessary at all for older kernels than
3.13....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2014-08-20 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 0:16 Dave Chinner [this message]
2014-09-13 1:44 ` XFS fixes needed in stable kernels 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=20140820001623.GT20518@dastard \
--to=david@fromorbit.com \
--cc=fanael4@gmail.com \
--cc=stable@vger.kernel.org \
--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.