From: deepakroag <gaikwad.dcg@gmail.com>
To: Viacheslav Dubeyko <slava@dubeyko.com>
Cc: ceph-devel@vger.kernel.org, Ilya Dryomov <idryomov@gmail.com>,
Alex Markuze <amarkuze@redhat.com>
Subject: Re: [PATCH 4/4] fix: release unused ceph cap reservation on readdir error
Date: Wed, 15 Jul 2026 23:56:41 +0530 [thread overview]
Message-ID: <20260715182641.34280-1-gaikwad.dcg@gmail.com> (raw)
In-Reply-To: <20260715181625.18677-1-gaikwad.dcg@gmail.com>
Hi Slava,
A quick clarification on my testing note from the previous reply — I worded
it poorly.
Testing: I compile-smoke-tested this change via ./scripts/vm-test.sh quick
in a Lima Ubuntu 24.04 arm64 VM before sending (checkpatch on the commit
plus building fs/ceph/inode.o along with the other touched objects in that
script). The run passed on 2026-07-15T18:25:58Z (2026-07-15 23:55:58 IST).
I do not have a Ceph cluster/MicroCeph environment to runtime-reproduce the
readdir error path or observe cap unreservation behavior under failure —
that remains static analysis from code review.
No further patch changes from this; the [PATCH 1/1] submission stands.
Thanks,
Deepak Rao Gaikwad
prev parent reply other threads:[~2026-07-15 18:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260715143646.15828-1-gaikwad.dcg@gmail.com>
2026-07-15 14:36 ` [PATCH 4/4] ceph: release unused cap reservation on readdir error deepakraog
2026-07-15 17:51 ` Viacheslav Dubeyko
2026-07-15 18:16 ` [PATCH] fix: release unused ceph " deepakroag
2026-07-16 17:24 ` Viacheslav Dubeyko
2026-07-15 18:16 ` [PATCH 4/4] " deepakroag
2026-07-15 18:26 ` deepakroag [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=20260715182641.34280-1-gaikwad.dcg@gmail.com \
--to=gaikwad.dcg@gmail.com \
--cc=amarkuze@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=idryomov@gmail.com \
--cc=slava@dubeyko.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