Re: [PATCH] reiserfs: only call unlock_new_inode() if I_NEW

2020-09-16 Thread Jan Kara
On Tue 15-09-20 21:01:18, Eric Biggers wrote: > On Mon, Jul 27, 2020 at 09:52:15AM -0700, Eric Biggers wrote: > > On Sun, Jun 28, 2020 at 12:00:57AM -0700, Eric Biggers wrote: > > > From: Eric Biggers > > > > > > unlock_new_inode() is only meant to be called after a new inode has > > > already

Re: [PATCH] reiserfs: only call unlock_new_inode() if I_NEW

2020-09-15 Thread Eric Biggers
On Mon, Jul 27, 2020 at 09:52:15AM -0700, Eric Biggers wrote: > On Sun, Jun 28, 2020 at 12:00:57AM -0700, Eric Biggers wrote: > > From: Eric Biggers > > > > unlock_new_inode() is only meant to be called after a new inode has > > already been inserted into the hash table. But

Re: [PATCH] reiserfs: only call unlock_new_inode() if I_NEW

2020-07-27 Thread Eric Biggers
On Sun, Jun 28, 2020 at 12:00:57AM -0700, Eric Biggers wrote: > From: Eric Biggers > > 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

[PATCH] reiserfs: only call unlock_new_inode() if I_NEW

2020-06-28 Thread Eric Biggers
From: Eric Biggers 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