Re: [PATCH (v4.18 regression fix)] vfs: don't evict uninitialized inode

2018-07-06 Thread Al Viro
On Fri, Jul 06, 2018 at 05:35:48PM +0200, Miklos Szeredi wrote: > 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 after the inode has been inserted into the > hash. The exact point at

Re: [PATCH (v4.18 regression fix)] vfs: don't evict uninitialized inode

2018-07-06 Thread Al Viro
On Fri, Jul 06, 2018 at 05:35:48PM +0200, Miklos Szeredi wrote: > 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 after the inode has been inserted into the > hash. The exact point at

[PATCH (v4.18 regression fix)] vfs: don't evict uninitialized inode

2018-07-06 Thread Miklos Szeredi
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 after the inode has been inserted into the hash. The exact point at which the inode is added onto the sb list shouldn't matter as long as it is

[PATCH (v4.18 regression fix)] vfs: don't evict uninitialized inode

2018-07-06 Thread Miklos Szeredi
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 after the inode has been inserted into the hash. The exact point at which the inode is added onto the sb list shouldn't matter as long as it is