diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2025-03-15 08:32:16 -1000 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2025-03-15 08:32:16 -1000 |
commit | eb88e6bfbc0a975e08a18c39d1138d3e6cdc00a5 (patch) | |
tree | 14000010282776092245e366fd60ad3a87cf9af4 /security/keys/gc.c | |
parent | 3571e8b091f4270d869dda7a6cc43616c6ad6897 (diff) | |
parent | 252256e416deb255607f0c4a69e7cfec079e5d61 (diff) | |
download | lwn-master.tar.gz lwn-master.zip |
Merge tag 'fsnotify_for_v6.14-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fsHEADmaster
Pull fsnotify reverts from Jan Kara:
"Syzbot has found out that fsnotify HSM events generated on page fault
can be generated while we already hold freeze protection for the
filesystem (when you do buffered write from a buffer which is mmapped
file on the same filesystem) which violates expectations for HSM
events and could lead to deadlocks of HSM clients with filesystem
freezing.
Since it's quite late in the cycle we've decided to revert changes
implementing HSM events on page fault for now and instead just
generate one event for the whole range on mmap(2) so that HSM client
can fetch the data at that moment"
* tag 'fsnotify_for_v6.14-rc7' of git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs:
Revert "fanotify: disable readahead if we have pre-content watches"
Revert "mm: don't allow huge faults for files with pre content watches"
Revert "fsnotify: generate pre-content permission event on page fault"
Revert "xfs: add pre-content fsnotify hook for DAX faults"
Revert "ext4: add pre-content fsnotify hook for DAX faults"
fsnotify: add pre-content hooks on mmap()
Diffstat (limited to 'security/keys/gc.c')
0 files changed, 0 insertions, 0 deletions