From: Miklos Szeredi <mszeredi@redhat.com>
To: linux-fsdevel@vger.kernel.org
Cc: Bernd Schubert <bschubert@ddn.com>,
Amir Goldstein <amir73il@gmail.com>,
Chunsheng Luo <luochunsheng@ustc.edu>,
Florian Weimer <fweimer@redhat.com>
Subject: [PATCH v2 0/3] fuse copy_file_range() fixes
Date: Wed, 13 Aug 2025 17:20:10 +0200 [thread overview]
Message-ID: <20250813152014.100048-1-mszeredi@redhat.com> (raw)
Fix 32 bit overflow issues.
v2:
- check for return value not exceeding requested size [1/3]
- split patch: limit copy size for old API [2/3], add new API [3/3]
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
---
Miklos Szeredi (3):
fuse: check if copy_file_range() returns larger than requested size
fuse: prevent overflow in copy_file_range return value
fuse: add COPY_FILE_RANGE_64 that allows large copies
fs/fuse/file.c | 39 +++++++++++++++++++++++++++++++--------
fs/fuse/fuse_i.h | 3 +++
include/uapi/linux/fuse.h | 12 +++++++++++-
3 files changed, 45 insertions(+), 9 deletions(-)
--
2.49.0
next reply other threads:[~2025-08-13 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 15:20 Miklos Szeredi [this message]
2025-08-13 15:20 ` [PATCH v2 1/3] fuse: check if copy_file_range() returns larger than requested size Miklos Szeredi
2025-08-13 15:20 ` [PATCH v2 2/3] fuse: prevent overflow in copy_file_range return value Miklos Szeredi
2025-08-13 15:20 ` [PATCH v2 3/3] fuse: add COPY_FILE_RANGE_64 that allows large copies Miklos Szeredi
2025-08-13 17:03 ` Joanne Koong
2025-08-13 17:18 ` Miklos Szeredi
2025-08-13 19:21 ` Florian Weimer
2025-08-13 20:35 ` Joanne Koong
2025-08-13 21:23 ` Florian Weimer
2025-08-14 17:04 ` Darrick J. Wong
2025-08-14 17:53 ` Joanne Koong
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=20250813152014.100048-1-mszeredi@redhat.com \
--to=mszeredi@redhat.com \
--cc=amir73il@gmail.com \
--cc=bschubert@ddn.com \
--cc=fweimer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=luochunsheng@ustc.edu \
/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 NNTP newsgroup(s).