Re: btrfs "possible irq lock inversion dependency detected"
Chris Murphy <[email protected]>
| Newsgroups | org.kernel.vger.trinity,org.kernel.vger.linux-btrfs,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On Feb 17, 2014, at 1:09 PM, Tommi Rantala <[email protected]> wrote: > Hello, > > Saw this while fuzzing the kernel with Trinity. > > Tommi > > > [ 396.136048] ========================================================= > [ 396.136048] [ INFO: possible irq lock inversion dependency detected ] > [ 396.136048] 3.14.0-rc3 #1 Not tainted > [ 396.136048] --------------------------------------------------------- > [ 396.136048] kswapd0/1482 just changed the state of lock: > [ 396.136048] (&delayed_node->mutex){+.+.-.}, at: [<ffffffff8147b83b>] __btrfs_release_delayed_node+0x4b/0x1e0 > [ 396.136048] but this lock took another, RECLAIM_FS-unsafe lock in the past: > [ 396.136048] (&found->groups_sem){+++++.} Looks like this is the same thing previously report on Btrfs list with 3.14.0-rc1 here: https://bugzilla.redhat.com/show_bug.cgi?id=1062439 Which points to this: https://bugzilla.redhat.com/show_bug.cgi?id=1062833#c24 Which points to this patch: http://marc.info/?l=linux-netdev&m=139233546723342&q=raw Chris Murphy