From: Al Viro <viro@ZenIV.linux.org.uk>
To: Li Zhong <zhong@linux.vnet.ibm.com>
Cc: linux-next list <linux-next@vger.kernel.org>
Subject: Re: [RFC PATCH next] fix unpaired rcu lock in prepend_path()
Date: Wed, 13 Nov 2013 12:28:48 +0000 [thread overview]
Message-ID: <20131113122848.GZ13318@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1384327311.19669.8.camel@ThinkPad-T5421>
On Wed, Nov 13, 2013 at 03:21:51PM +0800, Li Zhong wrote:
> The patch tries to fix following complaint(next-1112) caused by unpaired
> rcu_read_lock/unlock in function prepend_path():
Frankly, I wonder if it wouldn't be better to shift rcu_read_unlock()
past the second done_seqretry() in there...
next prev parent reply other threads:[~2013-11-13 12:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 7:21 [RFC PATCH next] fix unpaired rcu lock in prepend_path() Li Zhong
2013-11-13 12:28 ` Al Viro [this message]
2013-11-14 2:17 ` Li Zhong
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=20131113122848.GZ13318@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-next@vger.kernel.org \
--cc=zhong@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).