Re: [PATCH 0/2] fs: honor FOP_UNSIGNED_OFFSET in llseek and positional I/O

[Christian Brauner]

On Thu, 17 Sep 2026 17:16:12 +0200, Stian Halseth wrote:
> Two generic VFS bugs found while fixing pldd(1) on sparc64, where
> userspace is mapped above 2^63 so file positions on /proc/PID/mem have
> the top bit set.
> 
> FOP_UNSIGNED_OFFSET declares a file's offsets unsigned, and vfs_llseek(),
> rw_verify_area() and the mmap path honor it.  Two sets of syscall
> wrappers do not:
> 
> [...]

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/2] fs: fix llseek() result for files with unsigned offsets
      https://git.kernel.org/vfs/vfs/c/34e5caa86b12
[2/2] fs: allow positional I/O on files with unsigned offsets
      https://git.kernel.org/vfs/vfs/c/8c5ba5aa0278