diff options
| author | Eric Biggers <[email protected]> | 2020-06-28 00:00:57 -0700 |
|---|---|---|
| committer | Jan Kara <[email protected]> | 2020-09-16 12:51:24 +0200 |
| commit | 8859bf2b1278d064a139e3031451524a49a56bd0 (patch) | |
| tree | f425f831fd1fcda373d16da65d79a1ac3caf13cb /tools/perf/scripts/python/bin/export-to-postgresql-report | |
| parent | c53ec7bcc780fde4916e7a563d68b90b20b0b6bc (diff) | |
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/[email protected]
Reported-by: [email protected]
Signed-off-by: Eric Biggers <[email protected]>
Signed-off-by: Jan Kara <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/bin/export-to-postgresql-report')
0 files changed, 0 insertions, 0 deletions