From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: stable@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 0/9] XFS update for 3.0-stable
Date: Sat, 19 Nov 2011 10:59:19 -0800 [thread overview]
Message-ID: <20111119185919.GA30186@kroah.com> (raw)
In-Reply-To: <20111119181336.964593075@bombadil.infradead.org>
On Sat, Nov 19, 2011 at 01:13:36PM -0500, Christoph Hellwig wrote:
> This is the series of XFS fixes from current mainline which is important
> enough for 3.0-stable. All but the first three would also be needed
> for 3.1-stable, but given the limited resources I plan to concentrate
> on 3.0-stable. If anyone wants to take care for 3.1 by building a kernel
> with the remaining patches and run QA on them you are more welcome to
> help out with that tree.
>
> Note that while the description of
>
> xfs: don't serialise direct IO reads on page cache checks
>
> doesn't mention that is is a regression fix we later noticed that a
> large part of the speedups wasn't in fact new, but fixed a performance
> regression introduced in Linux 2.6.38 with commit:
>
> xfs: introduce xfs_rw_lock() helpers for locking the inode
Thanks for the series of patches, I'll queue them up after this latest
3.0 release happens on Monday.
greg k-h
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-11-19 19:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-19 18:13 [PATCH 0/9] XFS update for 3.0-stable Christoph Hellwig
2011-11-19 18:13 ` [PATCH 1/9] [PATCH 1/9] "xfs: fix error handling for synchronous writes" Christoph Hellwig
2011-11-19 18:13 ` [PATCH 2/9] [PATCH 2/9] xfs: fix xfs_mark_inode_dirty during umount Christoph Hellwig
2011-11-19 18:13 ` [PATCH 3/9] [PATCH 3/9] xfs: fix ->write_inode return values Christoph Hellwig
2011-11-19 18:13 ` [PATCH 4/9] [PATCH 4/9] xfs: dont serialise direct IO reads on page cache Christoph Hellwig
2011-11-22 21:34 ` Greg KH
2011-11-22 21:35 ` Greg KH
2011-11-19 18:13 ` [PATCH 5/9] [PATCH 5/9] xfs: avoid direct I/O write vs buffered I/O race Christoph Hellwig
2011-11-19 18:13 ` [PATCH 6/9] [PATCH 6/9] xfs: Return -EIO when xfs_vn_getattr() failed Christoph Hellwig
2011-11-19 18:13 ` [PATCH 7/9] [PATCH 7/9] xfs: fix buffer flushing during unmount Christoph Hellwig
2011-11-19 18:13 ` [PATCH 8/9] [PATCH 8/9] xfs: Fix possible memory corruption in xfs_readlink Christoph Hellwig
2011-11-19 18:13 ` [PATCH 9/9] [PATCH 9/9] xfs: use doalloc flag in xfs_qm_dqattach_one() Christoph Hellwig
2011-11-19 18:59 ` Greg KH [this message]
2011-11-21 0:46 ` [PATCH 0/9] XFS update for 3.0-stable Dave Chinner
2011-11-21 16:05 ` 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=20111119185919.GA30186@kroah.com \
--to=greg@kroah.com \
--cc=hch@infradead.org \
--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