* Re: [PATCH] io_uring: ensure that fsnotify is always called
[not found] <[email protected]>
@ 2022-03-20 19:43 ` Jens Axboe
0 siblings, 0 replies; only message in thread
From: Jens Axboe @ 2022-03-20 19:43 UTC (permalink / raw)
To: io-uring
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2022-03-20 19:43 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <[email protected]>
2022-03-20 19:43 ` [PATCH] io_uring: ensure that fsnotify is always called Jens Axboe
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox