Re: Circular lock dep in btrfs triggered by shrinker

2018-10-23 Thread Olof Johansson
On Mon, Oct 22, 2018 at 7:22 PM David Sterba wrote: > > On Mon, Oct 22, 2018 at 03:07:26AM -0700, Olof Johansson wrote: > > I hit the below circular locking dependency. Seems like the assumption made > > in > > 712e36c5f2a7fa56 ("btrfs: use GFP_KERNEL in btrfs_alloc_inode") either isn't > > true,

Re: Circular lock dep in btrfs triggered by shrinker

2018-10-23 Thread Michal Hocko
On Mon 22-10-18 20:22:43, David Sterba wrote: > On Mon, Oct 22, 2018 at 03:07:26AM -0700, Olof Johansson wrote: > > I hit the below circular locking dependency. Seems like the assumption made > > in > > 712e36c5f2a7fa56 ("btrfs: use GFP_KERNEL in btrfs_alloc_inode") either isn't > > true, or has s

Re: Circular lock dep in btrfs triggered by shrinker

2018-10-22 Thread David Sterba
On Mon, Oct 22, 2018 at 03:07:26AM -0700, Olof Johansson wrote: > I hit the below circular locking dependency. Seems like the assumption made in > 712e36c5f2a7fa56 ("btrfs: use GFP_KERNEL in btrfs_alloc_inode") either isn't > true, or has since changed? I think it must have been there from the beg

Circular lock dep in btrfs triggered by shrinker

2018-10-22 Thread Olof Johansson
Hi, I hit the below circular locking dependency. Seems like the assumption made in 712e36c5f2a7fa56 ("btrfs: use GFP_KERNEL in btrfs_alloc_inode") either isn't true, or has since changed? == WARNING: possible circular locking dependency detecte