From: Ben Myers <bpm@sgi.com>
To: greg@kroah.com, stable@vger.kernel.org
Cc: bpm@sgi.com, xfs@oss.sgi.com
Subject: XFS update for 3.1-stable (resent)
Date: Wed, 30 Nov 2011 12:10:54 -0600 [thread overview]
Message-ID: <1322676660-22945-1-git-send-email-bpm@sgi.com> (raw)
In-Reply-To: <20111128214018.GB1650@kroah.com>
Hey Greg,
The last mailing of this patch set went AWOL. Here's another whirl.
Greg K-H wrote:
> Was stable@vger.kernel.org on the to: line? If so, I should have seen them
> through that, but I don't, which is worrysome to me.
I thought so.
> The 3.0 series is already in the last 3.0.11 release, so I don't need them, I
> think I need the 3.1 patches, right?
Affirmative. You only need the 3.1 patches, here they are:
---
This is a series of XFS fixes from current mainline which are important for
3.1-stable. Note that it is the same patch set that Christoph submitted for
3.0-stable, minus the first three patches which are already included in 3.1.
My QA came out ok with these six patches atop 3.1.y.
Thanks!
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-30 17:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 21:38 [PATCH 0/6] XFS update for 3.1-stable Ben Myers
2011-11-23 21:38 ` [PATCH 1/6] xfs: don't serialise direct IO reads on page cache checks Ben Myers
2011-11-23 21:38 ` [PATCH 2/6] xfs: avoid direct I/O write vs buffered I/O race Ben Myers
2011-11-23 21:38 ` [PATCH 3/6] xfs: Return -EIO when xfs_vn_getattr() failed Ben Myers
2011-11-23 21:38 ` [PATCH 4/6] xfs: fix buffer flushing during unmount Ben Myers
2011-11-23 21:38 ` [PATCH 5/6] xfs: Fix possible memory corruption in xfs_readlink Ben Myers
2011-11-23 21:38 ` [PATCH 6/6] xfs: use doalloc flag in xfs_qm_dqattach_one() Ben Myers
2011-11-28 11:00 ` [PATCH 0/6] XFS update for 3.1-stable Christoph Hellwig
2011-11-28 13:48 ` Greg KH
2011-11-28 16:54 ` Ben Myers
2011-11-28 21:40 ` Greg KH
2011-11-30 18:10 ` Ben Myers [this message]
2011-11-30 18:10 ` [PATCH 1/6] xfs: don't serialise direct IO reads on page cache checks Ben Myers
2011-11-30 18:10 ` [PATCH 2/6] xfs: avoid direct I/O write vs buffered I/O race Ben Myers
2011-11-30 18:10 ` [PATCH 3/6] xfs: Return -EIO when xfs_vn_getattr() failed Ben Myers
2011-11-30 18:10 ` [PATCH 4/6] xfs: fix buffer flushing during unmount Ben Myers
2011-11-30 18:10 ` [PATCH 5/6] xfs: Fix possible memory corruption in xfs_readlink Ben Myers
2011-11-30 18:11 ` [PATCH 6/6] xfs: use doalloc flag in xfs_qm_dqattach_one() Ben Myers
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=1322676660-22945-1-git-send-email-bpm@sgi.com \
--to=bpm@sgi.com \
--cc=greg@kroah.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox