diff options
| author | Mateusz Guzik <mjg@FreeBSD.org> | 2025-10-05 17:02:01 +0000 |
|---|---|---|
| committer | Mateusz Guzik <mjg@FreeBSD.org> | 2025-10-05 21:21:10 +0000 |
| commit | f16178e0bba81c32b1f4fba310c7d0f2756aca85 (patch) | |
| tree | d9bfc0d8ea47426974628e847a37e9c02cc81317 | |
| parent | 03da141d59ae1da4e66974c466e2cb26f296e6df (diff) | |
vfs foffset: drop weird commentary about offset protection
It is readily apparent the FOFFSET_LOCKED flag protects it because the
read followed its use.
It also does not matter who said how it was protected earlier.
Reviewed by: kib, markj
Sponsored by: Rubicon Communications, LLC ("Netgate")
Differential Revision: https://reviews.freebsd.org/D52915
| -rw-r--r-- | sys/kern/vfs_vnops.c | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/sys/kern/vfs_vnops.c b/sys/kern/vfs_vnops.c index 3d4567b6ab1e..c2a669dc771a 100644 --- a/sys/kern/vfs_vnops.c +++ b/sys/kern/vfs_vnops.c @@ -864,10 +864,6 @@ foffset_lock(struct file *fp, int flags) FILE_V_FOFFSET_LOCK_WAITING); } - /* - * According to McKusick the vn lock was protecting f_offset here. - * It is now protected by the FOFFSET_LOCKED flag. - */ return (atomic_load_long(&fp->f_offset)); } |