JFFS2 deadlock with alloc_sem

[Dave Kleikamp]

On Tue, 2007-07-31 at 16:23 +0100, David Woodhouse wrote:
> On Tue, 2007-07-31 at 08:23 -0500, Dave Kleikamp wrote:
> > We had tried a similar patch, attached here, but it caused problems.
> > Maybe our patch is missing something.
> > 
> > >From the bug report:
> > -----------------------------
> > Built and ran the 2nd patch (attachment 28493 [edit]).  Results are similar
> > as before, jffs2 runs for a little while, but soon complains there's 
> > already data at the point where it intends to write. 
> > 
> > ARGH. About to write node to 0x00140010 on flash, but there's data already 
> > there:
> > 0x00140010: 19 85 e0 02 00 00 00 ac 0a 3e 48 74 00 00 00 74 
> 
> Hm, I think that's probably a _separate_ problem, which you happened to
> exacerbate. I don't see how it's related to f->sem locking.

Could be.  Remember this was on a 2.4 kernel as well, so mileage may
vary on the latest code.

Shaggy
-- 
David Kleikamp
IBM Linux Technology Center