From: Greg KH <gregkh@linuxfoundation.org>
To: hujianyang <hujianyang@huawei.com>
Cc: stable@vger.kernel.org, Li Zefan <lizefan@huawei.com>,
ben@decadent.org.uk, viro@zeniv.linux.org.uk
Subject: Re: [PATCH 2/2] deal with deadlock in d_walk()
Date: Sun, 26 Apr 2015 12:21:23 +0200 [thread overview]
Message-ID: <20150426102123.GA31776@kroah.com> (raw)
In-Reply-To: <54D31CD5.1070102@huawei.com>
On Thu, Feb 05, 2015 at 03:33:41PM +0800, hujianyang wrote:
> From: Al Viro <viro@zeniv.linux.org.uk>
>
> commit ca5358ef75fc69fee5322a38a340f5739d997c10 upstream.
>
> ... by not hitting rename_retry for reasons other than rename having
> happened. In other words, do _not_ restart when finding that
> between unlocking the child and locking the parent the former got
> into __dentry_kill(). Skip the killed siblings instead...
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> Cc: Ben Hutchings <ben@decadent.org.uk>
> [hujianyang: Backported to 3.10 refer to the work of Ben Hutchings in 3.2:
> - As we only have try_to_ascend() and not d_walk(), apply this
> change to all callers of try_to_ascend()
> - Adjust context to make __dentry_kill() apply to d_kill()]
> Signed-off-by: hujianyang <hujianyang@huawei.com>
> ---
> fs/dcache.c | 102 ++++++++++++++++++++++++++++++++++++-----------------------
> 1 files changed, 62 insertions(+), 40 deletions(-)
Can you provide a version for 3.14-stable as well?
thanks,
greg k-h
next parent reply other threads:[~2015-04-26 10:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54D31B6D.3070709@huawei.com>
[not found] ` <54D31CD5.1070102@huawei.com>
2015-04-26 10:21 ` Greg KH [this message]
2015-05-06 7:02 ` [PATCH 2/2] deal with deadlock in d_walk() hujianyang
2015-05-15 22:53 ` 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=20150426102123.GA31776@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ben@decadent.org.uk \
--cc=hujianyang@huawei.com \
--cc=lizefan@huawei.com \
--cc=stable@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.