On Thu, 07 Dec 2023 14:38:21 +0200, Amir Goldstein wrote: > I am not planning to post the fanotify pre-content event patches [1] > for 6.8. Not because they are not ready, but because the usersapce > example is not ready. > > Also, I think it is a good idea to let the large permission hooks > cleanup work to mature over the 6.8 cycle, before we introduce the > pre-content events. > > [...] Picking this up to get it into -next rather sooner than later. But @Jan, I'll wait for your Acks. --- Applied to the vfs.rw branch of the vfs/vfs.git tree. Patches in the vfs.rw branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.rw [1/4] fs: use splice_copy_file_range() inline helper https://git.kernel.org/vfs/vfs/c/4955c918c9e5 [2/4] fsnotify: split fsnotify_perm() into two hooks https://git.kernel.org/vfs/vfs/c/d2fc40363ab1 [3/4] fsnotify: assert that file_start_write() is not held in permission hooks https://git.kernel.org/vfs/vfs/c/24065342b941 [4/4] fsnotify: pass access range in file permission hooks https://git.kernel.org/vfs/vfs/c/e5c56a33657b
