From: Christian Brauner <brauner@kernel.org>
To: Marco Nelissen <marco.nelissen@gmail.com>
Cc: Christian Brauner <brauner@kernel.org>,
djwong@kernel.org, linux-xfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iomap: avoid avoid truncating 64-bit offset to 32 bits
Date: Thu, 9 Jan 2025 16:09:43 +0100 [thread overview]
Message-ID: <20250109-eishalle-sitte-b2b54d61839d@brauner> (raw)
In-Reply-To: <20250109041253.2494374-1-marco.nelissen@gmail.com>
On Wed, 08 Jan 2025 20:11:50 -0800, Marco Nelissen wrote:
> on 32-bit kernels, iomap_write_delalloc_scan() was inadvertently using a
> 32-bit position due to folio_next_index() returning an unsigned long.
> This could lead to an infinite loop when writing to an xfs filesystem.
>
>
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] iomap: avoid avoid truncating 64-bit offset to 32 bits
https://git.kernel.org/vfs/vfs/c/c13094b894de
prev parent reply other threads:[~2025-01-09 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 4:11 [PATCH] iomap: avoid avoid truncating 64-bit offset to 32 bits Marco Nelissen
2025-01-09 4:38 ` Darrick J. Wong
2025-01-09 4:45 ` Marco Nelissen
2025-01-09 4:47 ` Darrick J. Wong
2025-01-09 6:10 ` Christoph Hellwig
2025-01-09 15:09 ` Christian Brauner [this message]
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=20250109-eishalle-sitte-b2b54d61839d@brauner \
--to=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=marco.nelissen@gmail.com \
/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