From: Dan Carpenter <error27@gmail.com>
To: linux-fsdevel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Christian Brauner <brauner@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>
Subject: FOP_UNSIGNED_OFFSET abuse
Date: Thu, 21 May 2026 10:09:54 +0300 [thread overview]
Message-ID: <ag6vwpcCBN_VC1dm@stanley.mountain> (raw)
Is there a point to FOP_UNSIGNED_OFFSET now that everyone is on 64bit?
I thought the flag was for back in the day where we it was a huge deal
to access 4GB instead of 2GB.
It's mostly used in DRM. drm_open_helper() forces you to set the flag
but drm_read() ignores the offset so I don't understand the point of
this.
regards,
dan carpenter
$ git grep FOP_UNSIGNED_OFFSET
drivers/accel/amdxdna/amdxdna_pci_drv.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/char/adi.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/char/mem.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/adp/adp_drv.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/drm_file.c: if (WARN_ON_ONCE(!(filp->f_op->fop_flags & FOP_UNSIGNED_OFFSET)))
drivers/gpu/drm/gma500/psb_drv.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/i915/i915_driver.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/nouveau/nouveau_drm.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/panthor/panthor_drv.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/radeon/radeon_drv.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/tegra/drm.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c: .fop_flags = FOP_UNSIGNED_OFFSET,
drivers/gpu/drm/xe/xe_device.c: .fop_flags = FOP_UNSIGNED_OFFSET,
fs/proc/base.c: if (WARN_ON_ONCE(!(file->f_op->fop_flags & FOP_UNSIGNED_OFFSET)))
fs/proc/base.c: .fop_flags = FOP_UNSIGNED_OFFSET,
fs/read_write.c: return file->f_op->fop_flags & FOP_UNSIGNED_OFFSET;
include/drm/drm_accel.h: .fop_flags = FOP_UNSIGNED_OFFSET
include/drm/drm_gem.h: .fop_flags = FOP_UNSIGNED_OFFSET
include/drm/drm_gem_dma_helper.h: .fop_flags = FOP_UNSIGNED_OFFSET, \
include/linux/fs.h:#define FOP_UNSIGNED_OFFSET ((__force fop_flags_t)(1 << 5))
mm/mmap.c: if (file->f_op->fop_flags & FOP_UNSIGNED_OFFSET)
rust/bindings/bindings_helper.h:const fop_flags_t RUST_CONST_HELPER_FOP_UNSIGNED_OFFSET = FOP_UNSIGNED_OFFSET;
rust/kernel/drm/gem/mod.rs: fops.fop_flags = bindings::FOP_UNSIGNED_OFFSET;
next reply other threads:[~2026-05-21 7:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 7:09 Dan Carpenter [this message]
2026-05-21 8:36 ` FOP_UNSIGNED_OFFSET abuse Arnd Bergmann
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=ag6vwpcCBN_VC1dm@stanley.mountain \
--to=error27@gmail.com \
--cc=arnd@arndb.de \
--cc=brauner@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fsdevel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.