From: Al Viro <viro@ZenIV.linux.org.uk>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Michael Marineau <michael.marineau@coreos.com>,
Waiman Long <Waiman.Long@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: 3.12 Regression: dcache: Translating dentry into pathname without taking rename_lock 232d2d60
Date: Thu, 21 Nov 2013 23:22:42 +0000 [thread overview]
Message-ID: <20131121232242.GJ10323@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20131121230107.GA15179@kroah.com>
On Thu, Nov 21, 2013 at 03:01:07PM -0800, Greg KH wrote:
> Al, did this fix end up in Linus's tree yet? I'd like to pull it into
> the next 3.12-stable release, but will wait until Linus has it of
> course.
Yes - ede4ce.
next prev parent reply other threads:[~2013-11-21 23:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 11:34 3.12 Regression: dcache: Translating dentry into pathname without taking rename_lock 232d2d60 Michael Marineau
2013-11-13 12:39 ` Al Viro
2013-11-13 14:49 ` Long, Wai Man
2013-11-13 22:51 ` Michael Marineau
2013-11-21 23:01 ` Greg KH
2013-11-21 23:16 ` Michael Marineau
2013-11-22 19:45 ` Greg KH
2013-11-21 23:22 ` Al Viro [this message]
2013-11-22 19:45 ` 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=20131121232242.GJ10323@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=Waiman.Long@hp.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.marineau@coreos.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