diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2023-07-02 11:10:22 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2023-07-02 11:10:22 -0700 |
commit | 28c7980fa14a3fbd8926686cfffb89b9542b0da1 (patch) | |
tree | 0f0e7dbc2e2c9e6f519d8fedf82e9b2034e2d22f /fs/iomap | |
parent | 5def00ca25fa5697cfe352e675dc7c03116b2403 (diff) | |
parent | dff745c1221a402b4921d54f292288373cff500c (diff) | |
download | lwn-28c7980fa14a3fbd8926686cfffb89b9542b0da1.tar.gz lwn-28c7980fa14a3fbd8926686cfffb89b9542b0da1.zip |
Merge tag 'v6.5/vfs.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs
Pull vfs fix from Christian Brauner:
"A fix for the backing file work from this cycle.
When init_file() failed it would call file_free_rcu() on the file
allocated by the caller of init_file(). It naively assumed that the
correct cleanup operation would be called depending on whether it is a
regular file or a backing file. However, that presupposes that the
FMODE_BACKING flag would already be set which it won't be as that is
done in the caller of init_file().
Fix that bug by moving the cleanup of the allocated file into the
caller where it belongs in the first place. There's no good reason for
init_file() to consume resources it didn't allocate. This is a
mainline only fix and was reported by syzbot. The fix was validated by
syzbot against the provided reproducer"
* tag 'v6.5/vfs.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs:
fs: move cleanup from init_file() into its callers
Diffstat (limited to 'fs/iomap')
0 files changed, 0 insertions, 0 deletions