From: Alex Markuze <amarkuze@redhat.com>
To: Xiubo Li <xiubo.li@clyso.com>
Cc: Ilya Dryomov <idryomov@gmail.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org,
Anthony D'Atri <anthony.datri@gmail.com>
Subject: Re: [PATCH 0/2] ceph: serialize O_APPEND writes across clients
Date: Sun, 22 Nov 2026 18:25:49 +0000 [thread overview]
Message-ID: <20261122182549.1297448-1-amarkuze@redhat.com> (raw)
In-Reply-To: <20261121-ceph-append-excl-v1-0-5870375edeb8@clyso.com>
Hi Xiubo,
The feature check happens once before ceph_get_append_caps(). If an
append starts waiting on an MDS that supports APPEND_EXCL and the auth
cap migrates to an MDS without that feature, ceph_append_kick() keeps
asking for Fx. With another writer active, the older MDS can stay in MIX
and grant Fw without Fx, so the append keeps waiting while holding
i_rwsem.
Could the waiter recheck the current auth session's features and fall
back to the existing Fw-only path once an open session is known not to
support APPEND_EXCL? That would preserve the existing older-MDS behavior
instead of leaving the write waiting after migration.
Thanks,
Alex
prev parent reply other threads:[~2026-11-22 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 1:21 Xiubo Li via B4 Relay
2026-11-21 1:21 ` [PATCH 1/2] ceph: send the cap messages of an inode in the order they were prepared Xiubo Li via B4 Relay
2026-11-21 1:21 ` [PATCH 2/2] ceph: serialize O_APPEND writes across clients on Fx Xiubo Li via B4 Relay
2026-11-22 18:25 ` Alex Markuze [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=20261122182549.1297448-1-amarkuze@redhat.com \
--to=amarkuze@redhat.com \
--cc=anthony.datri@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=xiubo.li@clyso.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 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®