summaryrefslogtreecommitdiffstats
path: root/fs/udf
diff options
context:
space:
mode:
authorEric Biggers <ebiggers@google.com>2020-06-28 00:00:57 -0700
committerJan Kara <jack@suse.cz>2020-09-16 12:51:24 +0200
commit8859bf2b1278d064a139e3031451524a49a56bd0 (patch)
treef425f831fd1fcda373d16da65d79a1ac3caf13cb /fs/udf
parentc53ec7bcc780fde4916e7a563d68b90b20b0b6bc (diff)
downloadlinux-8859bf2b1278d064a139e3031451524a49a56bd0.tar.bz2
reiserfs: only call unlock_new_inode() if I_NEW
unlock_new_inode() is only meant to be called after a new inode has already been inserted into the hash table. But reiserfs_new_inode() can call it even before it has inserted the inode, triggering the WARNING in unlock_new_inode(). Fix this by only calling unlock_new_inode() if the inode has the I_NEW flag set, indicating that it's in the table. This addresses the syzbot report "WARNING in unlock_new_inode" (https://syzkaller.appspot.com/bug?extid=187510916eb6a14598f7). Link: https://lore.kernel.org/r/20200628070057.820213-1-ebiggers@kernel.org Reported-by: syzbot+187510916eb6a14598f7@syzkaller.appspotmail.com Signed-off-by: Eric Biggers <ebiggers@google.com> Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'fs/udf')
0 files changed, 0 insertions, 0 deletions