From: Tom Talpey <tom@talpey.com>
To: Christian Brauner <brauner@kernel.org>, NeilBrown <neil@brown.name>
Cc: Paulo Alcantara <pc@manguebit.org>,
Namjae Jeon <linkinjeon@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Jeff Layton <jlayton@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org, linux-cifs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] smb/client(cifs): prepare for locking changes.
Date: Wed, 21 Oct 2026 11:31:53 -0400 [thread overview]
Message-ID: <655e5d4f-7890-4956-88d2-cb571be218d6@talpey.com> (raw)
In-Reply-To: <20261021-sodbrennen-ausdruck-kurven-72d0b7cc7db9@brauner>
On 10/21/2026 5:55 AM, Christian Brauner wrote:
> On Mon, Sep 28, 2026 at 11:25:01AM +1000, NeilBrown wrote:
>> I am working on changes to directory locking. The medium term goal is
>> to lift d_alloc_parallel() locking above i_rwsem, so d_alloc_paralle()
>> can be run unlocked, and consequently cannot be called when ->i_rwsem is
>> held.
>>
>> The requires:
>> 1/ that d_alloc_parallel() not be called while i_rwsem is held. cifs
>> does this in a couple of places. A new interface d_alloc_trylock()
>> is now available and can be used instead.
>>
>> 2/ a dentry must not be d_drop()ed while an operation is ongoing, as an
>> unlocked d_alloc_parallel() would then be able to create a new
>> dentry with the same name. In particular d_rehash() must be phased
>> out as it won't be safe. This particularly affects the mechanism to
>> block lookups/revalidates while an unlink/rename is happening. The
>> mechanism is changed to use one similar to how NFS addresses this
>> needed, though using the new LOOKUP_PRIVATE flag.
>>
>> The patches depend on patches recently added to the vfs tree. I would
>> prefer these land in that tree too with an Acked-by or similar from cifs
>> maintainers.
>
> Can do, will need an Ack.
I will defer to Paulo for the Ack, but for the series, modulo my nit
on DCACHE_BLOCKED:
Reviewed-by: Tom Talpey <tom@talpey.com>
prev parent reply other threads:[~2026-10-21 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 1:25 NeilBrown
2026-09-28 1:25 ` [PATCH 1/3] smb/client: don't unhash and rehash to prevent new opens NeilBrown
2026-10-21 15:30 ` Tom Talpey
2026-09-28 1:25 ` [PATCH 2/3] smb/client: use d_alloc_trylock in cifs_silly_fullpath() NeilBrown
2026-09-28 1:25 ` [PATCH 3/3] smb/client: Use d_alloc_trylock() in cifs_prime_dcache() NeilBrown
2026-10-21 9:55 ` [PATCH 0/3] smb/client(cifs): prepare for locking changes Christian Brauner
2026-10-21 15:31 ` Tom Talpey [this message]
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=655e5d4f-7890-4956-88d2-cb571be218d6@talpey.com \
--to=tom@talpey.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linkinjeon@kernel.org \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neil@brown.name \
--cc=pc@manguebit.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
all inboxes | Powered by JetHome®