JFFS2: Fix lack of locking in thread_should_wake()
authorDavid Woodhouse <David.Woodhouse@intel.com>
Fri, 7 Nov 2008 00:08:59 +0000 (00:08 +0000)
committerGreg Kroah-Hartman <gregkh@suse.de>
Thu, 13 Nov 2008 17:55:58 +0000 (09:55 -0800)
commitffda96ca180ee1def996fd9a63c5a3d620caf223
tree2a0ec49cfe89c1016de096438b1f984bcbd77835
parenta414c208c07d29b404d07665ea6ab1bc564ade42
JFFS2: Fix lack of locking in thread_should_wake()

commit b27cf88e9592953ae292d05324887f2f44979433 upstream

The thread_should_wake() function trawls through the list of 'very
dirty' eraseblocks, determining whether the background GC thread should
wake. Doing this without holding the appropriate locks is a bad idea.

OLPC Trac #8615

Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
fs/jffs2/background.c