Re: jffs2 deadlock introduced in linux 2.6.22.5

On Thu, Aug 30, 2007 at 11:23:55AM -0700, Jason Lunz wrote:
> commit 1d8715b388c978b0f1b1bf4812fcee0e73b023d7 was added between
> 2.6.22.4 and 2.6.22.5 to cure a locking problem, but it seems to have
> introduced another (worse?) one.

I spoke too soon. I checked more carefully, and this problem was
introduced somewhere between 2.6.21 and 2.6.22. The jffs2 fix in
2.6.22.5 isn't the culprit.

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

---

• Follow-Ups:
  • [jffs2] [rfc] fix write deadlock regression
    • From: Jason Lunz <[email protected]>
  • Re: jffs2 deadlock introduced in linux 2.6.22.5
    • From: "Jesper Juhl" <[email protected]>

• References:
  • jffs2 deadlock introduced in linux 2.6.22.5
    • From: Jason Lunz <[email protected]>

• Prev by Date: Re: [PATCH] net/, drivers/net/ , missing EXPERIMENTAL in menus
• Next by Date: Re: jffs2 deadlock introduced in linux 2.6.22.5
• Previous by thread: jffs2 deadlock introduced in linux 2.6.22.5
• Next by thread: Re: jffs2 deadlock introduced in linux 2.6.22.5
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]