From: Ilya Dryomov <idryomov@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: ceph-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Ceph fixes for 6.11-rc1
Date: Fri, 26 Jul 2024 16:42:11 +0200 [thread overview]
Message-ID: <20240726144215.738251-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit 0c3836482481200ead7b416ca80c68a29cfdaabd:
Linux 6.10 (2024-07-14 15:43:32 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.11-rc1
for you to fetch changes up to 3ceccb14f5576e02b81cc8b105ab81f224bd87f6:
rbd: don't assume rbd_is_lock_owner() for exclusive mappings (2024-07-25 12:18:29 +0200)
----------------------------------------------------------------
A small patchset to address bogus I/O errors and ultimately an
assertion failure in the face of watch errors with -o exclusive
mappings in RBD marked for stable and some assorted CephFS fixes.
----------------------------------------------------------------
Chen Ni (1):
ceph: convert comma to semicolon in __ceph_dentry_dir_lease_touch()
Ilya Dryomov (3):
rbd: rename RBD_LOCK_STATE_RELEASING and releasing_wait
rbd: don't assume RBD_LOCK_STATE_LOCKED for exclusive mappings
rbd: don't assume rbd_is_lock_owner() for exclusive mappings
Max Kellermann (1):
ceph: use cap_wait_list only if debugfs is enabled
Xiubo Li (1):
ceph: periodically flush the cap releases
ethanwu (1):
ceph: fix incorrect kmalloc size of pagevec mempool
drivers/block/rbd.c | 35 +++++++++++++++--------------------
fs/ceph/caps.c | 6 ++++++
fs/ceph/dir.c | 2 +-
fs/ceph/mds_client.c | 4 ++++
fs/ceph/mds_client.h | 6 ++++++
fs/ceph/super.c | 3 ++-
6 files changed, 34 insertions(+), 22 deletions(-)
next reply other threads:[~2024-07-26 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-26 14:42 Ilya Dryomov [this message]
2024-07-26 18:07 ` pr-tracker-bot
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=20240726144215.738251-1-idryomov@gmail.com \
--to=idryomov@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®