From: Al Viro <viro@zeniv.linux.org.uk>
To: Mo Zou <lostzoumo@gmail.com>
Cc: brauner@kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] Documentation: fs: fix directory locking proofs
Date: Wed, 11 Oct 2023 07:46:08 +0100 [thread overview]
Message-ID: <20231011064608.GU800259@ZenIV> (raw)
In-Reply-To: <20231011052815.15022-1-lostzoumo@gmail.com>
On Wed, Oct 11, 2023 at 01:28:15PM +0800, Mo Zou wrote:
> Commit 28eceeda130f ("fs: Lock moved directories") acquires locks also for
> directories when they are moved and updates the deadlock-freedom proof
> to claim "a linear ordering of the objects - A < B iff (A is an ancestor
> of B) or (B is an ancestor of A and ptr(A) < ptr(B))". This claim,
> however, is not correct. Because cross-directory rename may acquire two
> parents (old parent and new parent) and two child directories (source
> and target) and the ordering between old parent and target (or new parent
> and source) may not fall into the above cases, i.e. ptr(old parent) <
> ptr(target) may not hold. We should revert to previous description that
> "at any moment we have a partial ordering of the objects - A < B iff A is
> an ancestor of B".
Not quite. I agree that the proof needs fixing, but your change doesn't
do it.
The thing is, the ordering in "neither is an ancestor of another" case
of lock_two_directories() does, unfortunately, matter. That's new,
subtle and not adequately discussed.
Another thing is that callers of lock_two_nondirectories() are not
covered at all.
I'll put something together and post it; it's 2:45am here at the moment,
and I'd rather get some sleep first.
next prev parent reply other threads:[~2023-10-11 6:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 5:28 [PATCH] Documentation: fs: fix directory locking proofs Mo Zou
2023-10-11 6:46 ` Al Viro [this message]
2023-10-11 14:11 ` Mo Zou
2023-10-11 19:06 ` 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=20231011064608.GU800259@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lostzoumo@gmail.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 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.