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.8-rc4
Date: Fri, 9 Feb 2024 16:34:57 +0100 [thread overview]
Message-ID: <20240209153458.1741231-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit 54be6c6c5ae8e0d93a6c4641cb7528eb0b6ba478:
Linux 6.8-rc3 (2024-02-04 12:20:36 +0000)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.8-rc4
for you to fetch changes up to 07045648c07c5632e0dfd5ce084d3cd0cec0258a:
ceph: always check dir caps asynchronously (2024-02-07 14:58:02 +0100)
----------------------------------------------------------------
Some fscrypt-related fixups (sparse reads are used only for encrypted
files) and two cap handling fixes from Xiubo and Rishabh.
----------------------------------------------------------------
Rishabh Dave (1):
ceph: prevent use-after-free in encode_cap_msg()
Xiubo Li (5):
libceph: fail sparse-read if the data length doesn't match
libceph: rename read_sparse_msg_*() to read_partial_sparse_msg_*()
libceph: just wait for more data to be available on the socket
ceph: always set initial i_blkbits to CEPH_FSCRYPT_BLOCK_SHIFT
ceph: always check dir caps asynchronously
fs/ceph/caps.c | 9 ++-------
fs/ceph/inode.c | 2 ++
fs/ceph/mds_client.c | 9 ++++-----
fs/ceph/mds_client.h | 2 +-
fs/ceph/super.h | 2 --
include/linux/ceph/messenger.h | 2 +-
include/linux/ceph/osd_client.h | 3 ++-
net/ceph/messenger_v1.c | 33 +++++++++++++++++----------------
net/ceph/messenger_v2.c | 4 ++--
net/ceph/osd_client.c | 27 ++++++++++++++++++---------
10 files changed, 49 insertions(+), 44 deletions(-)
next reply other threads:[~2024-02-09 15:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-09 15:34 Ilya Dryomov [this message]
2024-02-10 1:15 ` [GIT PULL] Ceph fixes for 6.8-rc4 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=20240209153458.1741231-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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).