[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OF7C1394C5.2BBD0A26-ONC1257F48.002BF506-C1257F48.002D6C9C@rohde-schwarz.com>
Date: Thu, 28 Jan 2016 09:16:08 +0100
From: Thomas.Betker@...de-schwarz.com
To: computersforpeace@...il.com
Cc: Artem Bityutskiy <dedekind1@...il.com>,
Deng Chao <deng.chao1@....com.cn>,
David Woodhouse <dwmw2@...radead.org>,
Joakim Tjernlund <Joakim.Tjernlund@...inera.com>,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"linux-mtd" <linux-mtd-bounces@...ts.infradead.org>,
Ming Liu <liu.ming50@...il.com>,
"sztomi89@...il.com" <sztomi89@...il.com>,
Thomas Betker <thomas.betker@...enet.de>,
Alexander Viro <viro@...iv.linux.org.uk>,
wangzaiwei <wangzaiwei@...-vision.cn>
Subject: Re: JFFS2 deadlock
Hello Brian:
> No, I'm pretty sure this is not the first report. I think there have
> even been patches. The problem is that JFFS2 is effectively
> unmaintained, despite what MAINTAINERS has to say about it.
>
> Previous reports:
>
> Subject: Another JFFS2 deadlock, kernel 3.4.11
> http://thread.gmane.org/gmane.linux.drivers.mtd/62523
>
> Subject: [JFFS2] Revision "jffs2: Fix lock acquisition order bug in
> jffs2_write_begin" introduces another dead lock.
> http://thread.gmane.org/gmane.linux.drivers.mtd/47986
> For reference: outstanding patches, waiting for a maintainer (I've been
> keeping patchwork up-to-date, mostly, but I'm not touching JFFS2 myself,
> for the most part):
> http://patchwork.ozlabs.org/project/linux-mtd/list/?q=jffs2
Subject: [PATCH] Revert "jffs2: Fix lock acquisition order bug in
jffs2_write_begin"
http://article.gmane.org/gmane.linux.drivers.mtd/62951
This is a patch revising my original patch, which I sent to linux-mtd on
10-Nov-2015. I didn't see a response yet, but it's one of the outstanding
patches above.
Best regards,
Thomas
Powered by blists - more mailing lists