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
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
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
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
4 matches
Mail list logo