From: Zach Brown <zab@zabbo.net>
To: Chris Kirby <ckirby@versity.com>
Cc: rpdfs-devel@lists.linux.dev
Subject: Re: [PATCH 1/1] Lock both inodes in rpdfs_unlink()
Date: Fri, 23 Oct 2026 10:33:09 -0700 [thread overview]
Message-ID: <20261023173309.GC1408936@localhost.localdomain> (raw)
In-Reply-To: <4012f89c8690987b6796af44d595138f3fa21ce3.1792433682.git.ckirby@versity.com>
On Mon, Oct 19, 2026 at 06:15:36PM +0000, Chris Kirby wrote:
> The code was only locking the parent directory inode. We also need to
> lock the inode being unlinked using rpdfs_inode_rlock_refresh_many().
Applied, thanks!
- z
prev parent reply other threads:[~2026-10-23 17:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 18:15 [PATCH 1/1] Lock both inodes in rpdfs_unlink() Chris Kirby
2026-10-23 17:33 ` Zach Brown [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=20261023173309.GC1408936@localhost.localdomain \
--to=zab@zabbo.net \
--cc=ckirby@versity.com \
--cc=rpdfs-devel@lists.linux.dev \
/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.