jffs2: Fix use of uninitialized delayed_work, lockdep breakage
authorDaniel Santos <daniel.santos@pobox.com>
Fri, 19 Oct 2018 08:59:20 +0000 (03:59 -0500)
committerHauke Mehrtens <hauke@hauke-m.de>
Sun, 16 Dec 2018 00:18:48 +0000 (01:18 +0100)
commit9850e4228400748dc91b07965b972279d45299d6
tree8247e1e89b0ab2080fd8b35a6d8761cbaf19c4ea
parent4bf5c4395b36456484c3b76d440d051f92938f96
jffs2: Fix use of uninitialized delayed_work, lockdep breakage

I've sent this one upstream.  This patch is critical if you want to run
with "prove lock correctness" (lockdep) and you happen to have certain
mtd devices.  The misuse of the uninitialized object is undefined
behaviour, but being zeroed it does not appear to have actually broken
anything other than the lockdep engine.

Signed-off-by: Daniel Santos <daniel.santos@pobox.com>
target/linux/generic/pending-4.14/142-jffs2-Fix-use-of-uninitialized-delayed_work-lockdep-.patch [new file with mode: 0644]
target/linux/generic/pending-4.14/530-jffs2_make_lzma_available.patch
target/linux/generic/pending-4.19/142-jffs2-Fix-use-of-uninitialized-delayed_work-lockdep-.patch [new file with mode: 0644]
target/linux/generic/pending-4.19/530-jffs2_make_lzma_available.patch