From: Christoph Hellwig <hch@infradead.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Ben Greear <greearb@candelatech.com>,
Christoph Hellwig <hch@infradead.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Crash in 3.14.0+ (plus hacks)
Date: Wed, 7 May 2014 08:02:46 -0700 [thread overview]
Message-ID: <20140507150246.GA19702@infradead.org> (raw)
In-Reply-To: <0D281678-A961-45B0-B1D7-49BDE6B3FC5C@oracle.com>
On Wed, May 07, 2014 at 10:31:10AM -0400, Chuck Lever wrote:
> > Probably it should be submitted to stable??
>
> Christoph has a broader fix for this issue, which affects more than
> just tmpfs. Stay tuned.
The fix has just made it into Linus' tree. I added a Cc: stable
tag, so it should get picked up soon.
prev parent reply other threads:[~2014-05-07 15:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 17:17 Crash in 3.14.0+ (plus hacks) Ben Greear
2014-04-11 19:18 ` Ben Greear
2014-04-25 10:48 ` J. Bruce Fields
2014-04-25 11:04 ` Christoph Hellwig
2014-04-25 13:30 ` Chuck Lever
2014-05-07 13:43 ` Ben Greear
2014-05-07 14:31 ` Chuck Lever
2014-05-07 15:02 ` Christoph Hellwig [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=20140507150246.GA19702@infradead.org \
--to=hch@infradead.org \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=greearb@candelatech.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).