Re: [PATCH] btrfs: nofs inode allocations

2019-10-01 Thread David Sterba
On Mon, Sep 09, 2019 at 10:12:04AM -0400, Josef Bacik wrote: > A user reported a lockdep splat > > == > WARNING: possible circular locking dependency detected > 5.2.11-gentoo #2 Not tainted > --

Re: [PATCH] btrfs: nofs inode allocations

2019-10-01 Thread David Sterba
On Mon, Sep 09, 2019 at 05:28:11PM +0300, Nikolay Borisov wrote: > > This is because btrfs_new_inode() calls new_inode() under the > > transaction. We could probably move the new_inode() outside of this but > > for now just wrap it in memalloc_nofs_save(). > > If I'm understanding correctly what

Re: [PATCH] btrfs: nofs inode allocations

2019-09-11 Thread Filipe Manana
On Tue, Sep 10, 2019 at 7:22 PM Josef Bacik wrote: > > A user reported a lockdep splat > > == > WARNING: possible circular locking dependency detected > 5.2.11-gentoo #2 Not tainted > -- >

Re: [PATCH] btrfs: nofs inode allocations

2019-09-09 Thread Nikolay Borisov
On 9.09.19 г. 17:12 ч., Josef Bacik wrote: > A user reported a lockdep splat > > == > WARNING: possible circular locking dependency detected > 5.2.11-gentoo #2 Not tainted > -- > kswapd0

[PATCH] btrfs: nofs inode allocations

2019-09-09 Thread Josef Bacik
A user reported a lockdep splat == WARNING: possible circular locking dependency detected 5.2.11-gentoo #2 Not tainted -- kswapd0/711 is trying to acquire lock: a663 (sb_intern