From: Al Viro <viro@zeniv.linux.org.uk>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH] vfs: make rename_lock per-sb
Date: Sun, 8 Dec 2019 05:54:11 +0000 [thread overview]
Message-ID: <20191208055411.GT4203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20191128154858.GA16668@miu.piliscsaba.redhat.com>
On Thu, Nov 28, 2019 at 04:48:58PM +0100, Miklos Szeredi wrote:
> Turning rename_lock into a per-sb lock mitigates the above issues.
... and completely fucks d_lookup(), since false negative can be
caused by rename of *ANYTHING* you've encountered while walking
a hash chain.
NAK.
next prev parent reply other threads:[~2019-12-08 5:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 15:48 [RFC PATCH] vfs: make rename_lock per-sb Miklos Szeredi
2019-12-08 5:54 ` Al Viro [this message]
2019-12-11 11:33 ` Miklos Szeredi
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=20191208055411.GT4203@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.