[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOQ4uxgOLEpaZ=UwA_CG6CzYbsJBPV4unEV9D5mXrooLXO0+0w@mail.gmail.com>
Date: Mon, 30 Jul 2018 08:09:19 +0300
From: Amir Goldstein <amir73il@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Miklos Szeredi <mszeredi@...hat.com>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 03/16] vfs: don't evict uninitialized inode
On Mon, Jul 30, 2018 at 1:04 AM, Al Viro <viro@...iv.linux.org.uk> wrote:
> From: Miklos Szeredi <mszeredi@...hat.com>
>
> iput() ends up calling ->evict() on new inode, which is not yet initialized
> by owning fs. So use destroy_inode() instead.
>
> Add to sb->s_inodes list only if inode is not in I_CREATING state (meaning
> that it wasn't allocated with new_inode(), which already does the
> insertion).
>
> Reported-by: Al Viro <viro@...iv.linux.org.uk>
> Signed-off-by: Miklos Szeredi <mszeredi@...hat.com>
> Fixes: 80ea09a002bf ("vfs: factor out inode_insert5()")
Backport hint: this patch depends on the patch ("new primitive:
discard_new_inode()") currently commit 22dc9a168272 in Al's for-next.
Still trying to figure out the best format to channel this information to
stable maintainers...
Thanks,
Amir.
Powered by blists - more mailing lists