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 7.2-rc8
Date: Fri, 14 Aug 2026 19:17:02 +0200 [thread overview]
Message-ID: <20260814171705.995932-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit db2ddb87143519e20a95aa36c60b36107b736a58:
Linux 7.2-rc7 (2026-08-09 14:54:50 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-7.2-rc8
for you to fetch changes up to 91880e4a7fac45bc407771bc57bbaf4f37e9b4c3:
ceph: use the mount idmap for the owner checks in the SET_LAYOUT ioctls (2026-08-12 21:21:41 +0200)
----------------------------------------------------------------
A handful of tiny fixes, with the main ones being a follow-up for
CEPH_IOC_SET_LAYOUT{,_POLICY} ioctl permissions check that went into
-rc5 and a userspace compatibility fixup. The rest mostly harden
against malformed network input. All marked for stable.
----------------------------------------------------------------
Kefu Chai (1):
libceph: tolerate addrvecs with multiple entries of the same type
Pavitra Jha (2):
libceph: fix multiple unsafe decodes in decode_locker()
libceph: fix OOB read in decode_watchers() via missing bounds check
Raphael Zimmer (1):
libceph: Avoid using invalid osd indices from primary_temp
Yiming Zhu (1):
ceph: fix MDS random selection readiness predicate
Zhan Xusheng (1):
ceph: use the mount idmap for the owner checks in the SET_LAYOUT ioctls
fs/ceph/ioctl.c | 4 ++--
fs/ceph/mdsmap.c | 2 +-
net/ceph/cls_lock_client.c | 13 +++++++++----
net/ceph/decode.c | 18 +++++++++---------
net/ceph/osd_client.c | 5 ++++-
net/ceph/osdmap.c | 5 +++--
6 files changed, 28 insertions(+), 19 deletions(-)
next reply other threads:[~2026-08-14 17:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-14 17:17 Ilya Dryomov [this message]
2026-08-14 17:43 ` 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=20260814171705.995932-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®