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 actuallyFWIW, what I propose is this (just the d_path-related parts):
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...