From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from www.tglx.de ([62.245.132.106]) by pentafluge.infradead.org with esmtps (Exim 4.63 #1 (Red Hat Linux)) id 1Ifhbg-0004Se-Hl for linux-mtd@lists.infradead.org; Wed, 10 Oct 2007 20:52:38 +0100 Date: Wed, 10 Oct 2007 21:51:22 +0200 (CEST) From: Thomas Gleixner To: Adrian Hunter Subject: Re: JFFS2 deadlock in erase callback In-Reply-To: <4709DF8E.1030707@nokia.com> Message-ID: References: <4709DF8E.1030707@nokia.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: "Bityutskiy Artem \\\(Nokia-M/Helsinki\\\)" , dwmw2@infradead.org, linux-mtd@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 8 Oct 2007, Adrian Hunter wrote: > [MTD] [NAND] Avoid deadlock in erase callback; release chip lock first. > > When the erase callback performs some other action on the flash, it's > highly likely to deadlock unless we actually release the chip lock > before calling it. > > Signed-off-by: David Woodhouse > > Can you confirm, that adding the "Avoid deadlock..." patch is better > than reverting "Reduce time..." patch. Yep, it's safe and definitely better. I remember vaguely that we planned/discussed to move the release before the callback some time ago, but the patch never made it into mainline. tglx