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.6-rc4
Date: Fri, 29 Sep 2023 16:59:36 +0200 [thread overview]
Message-ID: <20230929150002.264424-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit ce9ecca0238b140b88f43859b211c9fdfd8e5b70:
Linux 6.6-rc2 (2023-09-17 14:40:24 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.6-rc4
for you to fetch changes up to 0b207d02bd9ab8dcc31b262ca9f60dbc1822500d:
rbd: take header_rwsem in rbd_dev_refresh() only when updating (2023-09-26 10:33:19 +0200)
----------------------------------------------------------------
A series that fixes an involved "double watch error" deadlock in RBD
marked for stable and two cleanups.
----------------------------------------------------------------
Ilya Dryomov (5):
Revert "ceph: make members in struct ceph_mds_request_args_ext a union"
rbd: move rbd_dev_refresh() definition
rbd: decouple header read-in from updating rbd_dev->header
rbd: decouple parent info read-in from updating rbd_dev
rbd: take header_rwsem in rbd_dev_refresh() only when updating
Luís Henriques (1):
ceph: remove unnecessary check for NULL in parse_longname()
drivers/block/rbd.c | 412 +++++++++++++++++++++++--------------------
fs/ceph/crypto.c | 6 +-
include/linux/ceph/ceph_fs.h | 24 ++-
3 files changed, 238 insertions(+), 204 deletions(-)
next reply other threads:[~2023-09-29 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 14:59 Ilya Dryomov [this message]
2023-09-29 23:59 ` 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=20230929150002.264424-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®