Re: [PATCH] io_uring: ensure that fsnotify is always called

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 3/20/22 1:12 PM, Jens Axboe wrote:
> Ensure that we call fsnotify_modify() if we write a file, and that we
> do fsnotify_access() if we read it. This enables anyone using inotify
> on the file to get notified.
> 
> Ditto for fallocate, ensure that fsnotify_modify() is called.

Forgot to put in the patch notes - this is not new for io_uring, aio
never called fsnotify either. But we do have a much broader scope that
aio which is all db and dio. Would be nice to have this be opt-in or
similar, though at least the per-op hit doesn't seem to be that large if
nobody is has a notifier registered (which is 99.99% of the use
cases...).

-- 
Jens Axboe




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux