Re: [PATCH] jffs2: Fix lock acquisition order bug in gc path
From: Josh Cartwright
Date: Thu Mar 29 2012 - 19:42:25 EST
On Thu, Mar 29, 2012 at 08:38:41AM -0700, Brian Norris wrote:
> On Thu, Feb 9, 2012 at 10:50 AM, Josh Cartwright <joshc@xxxxxxxxx> wrote:
> > The locking policy is such that the erase_complete_block spinlock is
> > nested within the alloc_sem mutex. This fixes a case in which the
> > acquisition order was erroneously reversed. This issue was caught by
> > the following lockdep splat:
> (Bump.) Anybody interested in this patch? It seemed sane to me, and I
> had it sitting in my inbox. It does need a trivial rebase, BTW.
I'm certainly still interested in it, for what its worth :). We've had
no problems here for the month and a half its been in our tree.
I'll send out a rebased V2.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/