linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Waiman Long <waiman.long@hp.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Chandramouleeswaran, Aswin" <aswin@hp.com>,
	"Norton, Scott J" <scott.norton@hp.com>,
	George Spelvin <linux@horizon.com>,
	John Stoffel <john@stoffel.org>
Subject: Re: [PATCH v4 1/1] dcache: Translating dentry into pathname without taking rename_lock
Date: Mon, 09 Sep 2013 14:46:57 -0400	[thread overview]
Message-ID: <522E17A1.1020205@hp.com> (raw)
In-Reply-To: <20130909183608.GR13318@ZenIV.linux.org.uk>

On 09/09/2013 02:36 PM, Al Viro wrote:
> On Mon, Sep 09, 2013 at 07:21:11PM +0100, Al Viro wrote:
>> Actually, it's better for prepend_path() as well, because it's actually
>>
>> 	rcu_read_lock();
>> 	seq = read_seqbegin(&rename_lock);
>> again:
>> 	....
>> 	if (error)
>> 		goto done;
>> 	....
>> 	if (!seqretry_and_lock(&rename_lock, seq))
>> 		goto again;	/* now as writer */
>> done:
>> 	seqretry_done(&rename_lock, seq);
>> 	rcu_read_unlock();
>>
>> Posted variant will sometimes hit the following path:
>> 	* seq_readlock()
>> 	* start generating the output
>> 	* hit an error
>> [another process has taken and released rename_lock for some reason]
>> 	* hit read_seqretry_and_unlock(), which returns 1.
>> 	* retry everything with seq_writelock(), despite the error.
>>
>> It's not too horrible (we won't be looping indefinitely, ignoring error
>> all along), but it's certainly subtle enough...
> FWIW, what I propose is this (just the d_path-related parts):
>
>

I am fine with your proposed change as long as it gets the job done. It 
doesn't really matter if you do it or I do it.

Thank for taking the effort to make it better for us all.

-Longman

  parent reply	other threads:[~2013-09-09 18:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-09 16:18 [PATCH v4 0/1] dcache: Translating dentry into pathname without taking rename_lock Waiman Long
2013-09-09 16:18 ` [PATCH v4 1/1] " Waiman Long
2013-09-09 17:29   ` Al Viro
2013-09-09 17:45     ` Linus Torvalds
2013-09-09 17:56       ` Waiman Long
2013-09-09 18:06       ` Al Viro
2013-09-09 18:15         ` Linus Torvalds
2013-09-09 18:21         ` Al Viro
2013-09-09 18:36           ` Al Viro
2013-09-09 18:46             ` Al Viro
2013-09-09 18:46             ` Waiman Long [this message]
2013-09-09 19:10               ` Al Viro
2013-09-09 19:28                 ` Al Viro
2013-09-09 22:57                   ` Waiman Long
2013-09-10  0:40           ` George Spelvin
2013-09-10  0:57             ` Al Viro
2013-09-10  1:15               ` Ramkumar Ramachandra
2013-09-10  1:34                 ` Linus Torvalds
2013-09-10  2:25                   ` Al Viro
2013-09-10  2:33                     ` Linus Torvalds
2013-09-10  3:12                   ` Ramkumar Ramachandra
2013-09-10  8:24               ` George Spelvin
2013-09-10  3:57             ` Waiman Long
2013-09-09 17:55     ` Waiman Long
2013-09-09 18:07       ` Al Viro

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=522E17A1.1020205@hp.com \
    --to=waiman.long@hp.com \
    --cc=aswin@hp.com \
    --cc=john@stoffel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=scott.norton@hp.com \
    --cc=torvalds@linux-foundation.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 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).