From: Alex Markuze <amarkuze@redhat.com>
To: ceph-devel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Slava.Dubeyko@ibm.com,
idryomov@gmail.com, Alex Markuze <amarkuze@redhat.com>
Subject: [PATCH 0/2] ceph: Fix r_parent staleness race and related deadlock
Date: Mon, 4 Aug 2025 09:59:40 +0000 [thread overview]
Message-ID: <20250804095942.2167541-1-amarkuze@redhat.com> (raw)
Hi,
This patchset addresses two related issues in CephFS client request handling.
**Patch 1/2 ("ceph: fix client race condition where r_parent becomes stale before sending message")**
This patch fixes a race condition where the `req->r_parent` inode reference can become stale. Under specific conditions (e.g., expired dentry leases), the client can perform lockless lookups, creating a window where a concurrent `rename` operation can invalidate `req->r_parent` between initial VFS lookup and MDS request message creation. The MDS reply handler (`create_request_message`) previously trusted the cached `r_parent` without verification. This patch enhances path-building functions to track the full `ceph_vino` and adds a validation step in `create_request_message` to compare and correct `req->r_parent` if a mismatch is detected (when the parent wasn't locked).
**Patch 2/2 ("ceph: fix deadlock in ceph_readdir_prepopulate due to snap_rwsem")**
This patch fixes a deadlock in `ceph_readdir_prepopulate`. The function holds `mdsc->snap_rwsem` (read lock) while calling `ceph_get_inode`, which can potentially block on inode operations that might require the `snap_rwsem` write lock, leading to a classic reader/writer deadlock. This patch releases `mdsc->snap_rwsem` before calling `ceph_get_inode` and re-acquires it afterwards, breaking the deadlock cycle.
Together, these patches improve the robustness and stability of CephFS client request handling by fixing a correctness race and a critical deadlock.
Alex Markuze (2):
ceph: fix client race condition validating r_parent before applying
state
ceph: fix client race condition where r_parent becomes stale before
sending message
fs/ceph/inode.c | 44 +++++++++++++++++++++++++++--
fs/ceph/mds_client.c | 67 +++++++++++++++++++++++++++++++-------------
2 files changed, 89 insertions(+), 22 deletions(-)
--
2.34.1
next reply other threads:[~2025-08-04 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-04 9:59 Alex Markuze [this message]
2025-08-04 9:59 ` [PATCH v2 1/2] ceph: fix client race condition validating r_parent before applying state Alex Markuze
2025-08-04 21:44 ` Viacheslav Dubeyko
2025-08-04 9:59 ` [PATCH v2 2/2] ceph: fix client race condition where r_parent becomes stale before sending message Alex Markuze
2025-08-04 21:58 ` Viacheslav Dubeyko
2025-08-05 12:28 ` Alex Markuze
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=20250804095942.2167541-1-amarkuze@redhat.com \
--to=amarkuze@redhat.com \
--cc=Slava.Dubeyko@ibm.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®