mirror of
git://git.yoctoproject.org/linux-yocto.git
synced 2025-10-22 15:03:53 +02:00
fs: drop assert in file_seek_cur_needs_f_lock
The assert in function file_seek_cur_needs_f_lock() can be triggered very
easily because there are many users of vfs_llseek() (such as overlayfs)
that do their custom locking around llseek instead of relying on
fdget_pos(). Just drop the overzealous assertion.
Fixes: da06e3c517
("fs: don't needlessly acquire f_lock")
Suggested-by: Jan Kara <jack@suse.cz>
Suggested-by: Mateusz Guzik <mjguzik@gmail.com>
Signed-off-by: Luis Henriques <luis@igalia.com>
Link: https://lore.kernel.org/20250613101111.17716-1-luis@igalia.com
Signed-off-by: Christian Brauner <brauner@kernel.org>
This commit is contained in:
parent
0b9d62a471
commit
dd2d6b7f6f
|
@ -1198,8 +1198,12 @@ bool file_seek_cur_needs_f_lock(struct file *file)
|
|||
if (!(file->f_mode & FMODE_ATOMIC_POS) && !file->f_op->iterate_shared)
|
||||
return false;
|
||||
|
||||
VFS_WARN_ON_ONCE((file_count(file) > 1) &&
|
||||
!mutex_is_locked(&file->f_pos_lock));
|
||||
/*
|
||||
* Note that we are not guaranteed to be called after fdget_pos() on
|
||||
* this file obj, in which case the caller is expected to provide the
|
||||
* appropriate locking.
|
||||
*/
|
||||
|
||||
return true;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue
Block a user