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.19-rc9
Date: Fri, 6 Feb 2026 16:45:32 +0100 [thread overview]
Message-ID: <20260206154605.1369203-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit 18f7fcd5e69a04df57b563360b88be72471d6b62:
Linux 6.19-rc8 (2026-02-01 14:01:13 -0800)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.19-rc9
for you to fetch changes up to 7987cce375ac8ce98e170a77aa2399f2cf6eb99f:
ceph: fix NULL pointer dereference in ceph_mds_auth_match() (2026-02-04 22:00:42 +0100)
----------------------------------------------------------------
One RBD and two CephFS fixes which address potential oopses. The RBD
thing is more of a rare edge case that pops up in our CI, while the two
CephFS scenarios are regressions that were reported by users and can be
triggered trivially in normal operation. All marked for stable.
----------------------------------------------------------------
Daniel Vogelbacher (1):
ceph: fix oops due to invalid pointer for kfree() in parse_longname()
Ilya Dryomov (1):
rbd: check for EOD after exclusive lock is ensured to be held
Viacheslav Dubeyko (1):
ceph: fix NULL pointer dereference in ceph_mds_auth_match()
drivers/block/rbd.c | 33 +++++++++++++++++++++------------
fs/ceph/crypto.c | 9 +++++----
fs/ceph/mds_client.c | 5 +++--
fs/ceph/mdsmap.c | 26 +++++++++++++++++++-------
fs/ceph/mdsmap.h | 1 +
fs/ceph/super.h | 16 ++++++++++++++--
include/linux/ceph/ceph_fs.h | 6 ++++++
7 files changed, 69 insertions(+), 27 deletions(-)
next reply other threads:[~2026-02-06 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 15:45 Ilya Dryomov [this message]
2026-02-06 23:09 ` 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=20260206154605.1369203-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®