public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: <dedekind@infradead.org>, "'David Woodhouse'" <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org
Subject: RE: [PATCH] Revert "[JFFS2] Reduce time for which erase_free_sem isheld during erase."
Date: Fri, 5 Oct 2007 19:26:19 +0200	[thread overview]
Message-ID: <008401c80774$d8050eb0$0e67a8c0@Jocke> (raw)
In-Reply-To: <1191597989.4586.16.camel@sauron>

 > -----Original Message-----
> From: Artem Bityutskiy [mailto:dedekind@infradead.org] 
> Sent: den 5 oktober 2007 17:26
> To: David Woodhouse
> Cc: Joakim Tjernlund; linux-mtd@lists.infradead.org
> Subject: [PATCH] Revert "[JFFS2] Reduce time for which 
> erase_free_sem isheld during erase."
> 
> >From e1d782add3a72421eb637a119c594a6d9b774727 Mon Sep 17 
> 00:00:00 2001
> From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
> Date: Fri, 5 Oct 2007 20:09:45 +0300
> Subject: [PATCH] Revert "[JFFS2] Reduce time for which 
> erase_free_sem is held during erase."
> 
> This reverts commit d364fb18cd991734eb54aa8840e70030b0c9f699.
> 
> This patch locks up the system because it takes the 
> 'erase_free_sem' in
> the erase callback function, which is in turn called from NAND/OneNAND
> driver with NAND/OneNAND chip locked. Obviously, another process which
> holds 'erase_free_sem' and calls an I/O function will deadlock at the
> NAND/OneNAND chip lock. Below is the backtrace of this deadlock which
> we observed in practice:

uhh, I guess this problem is NAND specific? I don't think reverting
this patch is the answer. There got to be a better fix, as my patch
solves a real problem too.

 Jocke

  reply	other threads:[~2007-10-05 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 15:26 [PATCH] Revert "[JFFS2] Reduce time for which erase_free_sem is held during erase." Artem Bityutskiy
2007-10-05 17:26 ` Joakim Tjernlund [this message]
2007-10-05 21:00 ` David Woodhouse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='008401c80774$d8050eb0$0e67a8c0@Jocke' \
    --to=joakim.tjernlund@transmode.se \
    --cc=dedekind@infradead.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox