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.13-rc4
Date: Fri, 20 Dec 2024 20:40:54 +0100 [thread overview]
Message-ID: <20241220194104.1350097-1-idryomov@gmail.com> (raw)
Hi Linus,
The following changes since commit 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8:
Linux 6.13-rc3 (2024-12-15 15:58:23 -0800)
are available in the Git repository at:
https://github.com/ceph/ceph-client.git tags/ceph-for-6.13-rc4
for you to fetch changes up to 18d44c5d062b97b97bb0162d9742440518958dc1:
ceph: allocate sparse_ext map only for sparse reads (2024-12-16 23:25:44 +0100)
----------------------------------------------------------------
A handful of important CephFS fixes from Max, Alex and myself: memory
corruption due to a buffer overrun, potential infinite loop and several
memory leaks on the error paths. All but one marked for stable.
----------------------------------------------------------------
Alex Markuze (1):
ceph: improve error handling and short/overflow-read logic in __ceph_sync_read()
Ilya Dryomov (3):
ceph: validate snapdirname option length when mounting
ceph: fix memory leak in ceph_direct_read_write()
ceph: allocate sparse_ext map only for sparse reads
Max Kellermann (2):
ceph: fix memory leaks in __ceph_sync_read()
ceph: give up on paths longer than PATH_MAX
fs/ceph/file.c | 77 +++++++++++++++++++++++++--------------------------
fs/ceph/mds_client.c | 9 +++---
fs/ceph/super.c | 2 ++
net/ceph/osd_client.c | 2 ++
4 files changed, 46 insertions(+), 44 deletions(-)
next reply other threads:[~2024-12-20 19:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 19:40 Ilya Dryomov [this message]
2024-12-21 17:37 ` 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=20241220194104.1350097-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®