From: Christoph Hellwig <hch@lst.de>
To: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>
Cc: Jan Kara <jack@suse.cz>,
x86@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, sparclinux@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org
Subject: fix architecture-specific compat_ftruncate64 implementations
Date: Mon, 23 Mar 2026 08:01:43 +0100 [thread overview]
Message-ID: <20260323070205.2939118-1-hch@lst.de> (raw)
Hi all,
this series fixes a really old bug found by code inspection, where the
architecture-specific 32-bit compat ftruncate64 implementations enforce
the non-LFS file size limit unless opened with O_LARGEFILE.
Diffstat:
arch/arm64/kernel/sys32.c | 2 +-
arch/mips/kernel/linux32.c | 2 +-
arch/parisc/kernel/sys_parisc.c | 4 ++--
arch/powerpc/kernel/sys_ppc32.c | 2 +-
arch/sparc/kernel/sys_sparc32.c | 2 +-
arch/x86/kernel/sys_ia32.c | 3 ++-
fs/internal.h | 3 +--
fs/open.c | 40 +++++++++++++++++++---------------------
include/linux/syscalls.h | 16 +++-------------
io_uring/truncate.c | 2 +-
10 files changed, 32 insertions(+), 44 deletions(-)
next reply other threads:[~2026-03-23 7:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 7:01 Christoph Hellwig [this message]
2026-03-23 7:01 ` [PATCH 1/3] fs: fix archiecture-specific compat_ftruncate64 Christoph Hellwig
2026-03-23 10:27 ` Jan Kara
2026-03-23 7:01 ` [PATCH 2/3] fs: pass on FTRUNCATE_* flags to do_truncate Christoph Hellwig
2026-03-23 10:28 ` Jan Kara
2026-03-23 7:01 ` [PATCH 3/3] fs: remove do_sys_truncate Christoph Hellwig
2026-03-23 10:31 ` Jan Kara
2026-03-23 11:44 ` fix architecture-specific compat_ftruncate64 implementations Christian Brauner
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=20260323070205.2939118-1-hch@lst.de \
--to=hch@lst.de \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sparclinux@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.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