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.16-rc1
Date: Fri, 6 Jun 2025 19:52:35 +0200 [thread overview]
Message-ID: <20250606175250.218814-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit 0ff41df1cb268fc69e703a08a57ee14ae967d0ca:
Linux 6.15 (2025-05-25 16:09:23 -0700)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.16-rc1
for you to fetch changes up to b828b4bf29d10a3e505a76a39c4daea969e19dc9:
ceph: fix variable dereferenced before check in ceph_umount_begin() (2025-06-06 11:08:59 +0200)
----------------------------------------------------------------
A one-liner that leads to a startling (but also very much rational)
performance improvement in cases where an IMA policy with rules that
are based on fsmagic matching is enforced, an encryption-related fixup
that addresses generic/397 and other fstest failures and a couple of
cleanups in CephFS.
----------------------------------------------------------------
Dennis Marttinen (1):
ceph: set superblock s_magic for IMA fsmagic matching
Dmitry Kandybka (1):
ceph: fix possible integer overflow in ceph_zero_objects()
Viacheslav Dubeyko (3):
ceph: avoid kernel BUG for encrypted inode with unaligned file size
ceph: cleanup hardcoded constants of file handle size
ceph: fix variable dereferenced before check in ceph_umount_begin()
fs/ceph/addr.c | 9 +++++++++
fs/ceph/export.c | 21 +++++++++++++--------
fs/ceph/file.c | 2 +-
fs/ceph/super.c | 4 ++--
4 files changed, 25 insertions(+), 11 deletions(-)
next reply other threads:[~2025-06-06 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-06 17:52 Ilya Dryomov [this message]
2025-06-07 1:17 ` 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=20250606175250.218814-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®