From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: stable@kernel.org, xfs@oss.sgi.com
Subject: Re: [stable] [PATCH 0/4] 2.6.30-stable backport of the XFS+NFSD inode cache race fix
Date: Thu, 3 Sep 2009 15:19:58 -0700 [thread overview]
Message-ID: <20090903221958.GC23517@kroah.com> (raw)
In-Reply-To: <20090819184258.542698202@bombadil.infradead.org>
On Wed, Aug 19, 2009 at 02:42:58PM -0400, Christoph Hellwig wrote:
>
> This is a backport of the fix for the XFS inode cache races lots of people
> have reported. The context for the two VFS patches changed quite a bit from
> 2.6.30 to 2.6.31-rc so I consider these backports. The backport has been
> tested by me with xfstest for XFS and extN, and by lots of users that have
> been waiting for the fix for their nfs servers still running 2.6.30.
All queued up, thanks.
greg k-h
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-09-04 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-19 18:42 [PATCH 0/4] 2.6.30-stable backport of the XFS+NFSD inode cache race fix Christoph Hellwig
2009-08-19 18:42 ` [PATCH 1/4] vfs: fix inode_init_always calling convention Christoph Hellwig
2009-08-19 18:43 ` [PATCH 2/4] vfs: add __destroy_inode Christoph Hellwig
2009-08-19 18:43 ` [PATCH 3/4] xfs: fix freeing of inodes not yet added to the inode cache Christoph Hellwig
2009-08-19 18:43 ` [PATCH 4/4] xfs: fix spin_is_locked assert on uni-processor builds Christoph Hellwig
2009-09-03 22:19 ` Greg KH [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=20090903221958.GC23517@kroah.com \
--to=greg@kroah.com \
--cc=hch@infradead.org \
--cc=stable@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