Re: BUG: held lock freed! with 2.6.17-mm3 and 2.6.17-mm4

[Timothy Shimmin <tes@sgi.com>]

On Friday 30 June 2006 8:14 am, Nathan Scott wrote:
> On Thu, Jun 29, 2006 at 10:38:09PM +0200, Ralf Hildebrandt wrote:
> > 2.6.17-mm3 and mm4 both report a "BUG: held lock freed!" while booting
> > up. Find the two dmesg outputs attached.
>
> Thanks Ralf,
>
> >From the traces, looks like it happens during the unlinked inode list
>
> processing, just after log recovery (I assume you crashed / rebooted
> without unmounting before this boot?).  Tim, do you see any situation
> in recovery where we might have freed an inode while it was locked?

Had a look but I can't see anything apparent at this stage,
let's run our unlink recovery test on the -mm tree next week,
which should expose the bug.

--Tim

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/