Skip to content

Commit 8859bf2

Browse files
ebiggersjankara
authored andcommitted
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]>
1 parent c53ec7b commit 8859bf2

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

fs/reiserfs/inode.c

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2163,7 +2163,8 @@ int reiserfs_new_inode(struct reiserfs_transaction_handle *th,
21632163
out_inserted_sd:
21642164
clear_nlink(inode);
21652165
th->t_trans_id = 0; /* so the caller can't use this handle later */
2166-
unlock_new_inode(inode); /* OK to do even if we hadn't locked it */
2166+
if (inode->i_state & I_NEW)
2167+
unlock_new_inode(inode);
21672168
iput(inode);
21682169
return err;
21692170
}

0 commit comments

Comments
 (0)