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 -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
