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.18-rc8
Date: Thu, 27 Nov 2025 19:49:56 +0100 [thread overview]
Message-ID: <20251127184958.2776540-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit ac3fd01e4c1efce8f2c054cdeb2ddd2fc0fb150d:
Linux 6.18-rc7 (2025-11-23 14:53:16 -0800)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.18-rc8
for you to fetch changes up to 7fce830ecd0a0256590ee37eb65a39cbad3d64fc:
libceph: prevent potential out-of-bounds writes in handle_auth_session_key() (2025-11-27 09:59:49 +0100)
----------------------------------------------------------------
A patch to make sparse read handling work in msgr2 secure mode from
Slava and a couple of fixes from Ziming and myself to avoid operating
on potentially invalid memory, all marked for stable.
----------------------------------------------------------------
Ilya Dryomov (2):
libceph: fix potential use-after-free in have_mon_and_osd_map()
libceph: drop started parameter of __ceph_open_session()
Viacheslav Dubeyko (1):
ceph: fix crash in process_v2_sparse_read() for encrypted directories
ziming zhang (2):
libceph: replace BUG_ON with bounds check for map->max_osd
libceph: prevent potential out-of-bounds writes in handle_auth_session_key()
fs/ceph/super.c | 2 +-
include/linux/ceph/libceph.h | 3 +--
net/ceph/auth_x.c | 2 ++
net/ceph/ceph_common.c | 58 ++++++++++++++++++++++++++------------------
net/ceph/debugfs.c | 14 ++++++++---
net/ceph/messenger_v2.c | 11 ++++++---
net/ceph/osdmap.c | 18 ++++++++------
7 files changed, 66 insertions(+), 42 deletions(-)
next reply other threads:[~2025-11-27 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-27 18:49 Ilya Dryomov [this message]
2025-11-27 20:02 ` 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=20251127184958.2776540-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®