summaryrefslogtreecommitdiff
path: root/fs/jffs2/README.Locking
diff options
context:
space:
mode:
authorDavid Woodhouse <David.Woodhouse@intel.com>2008-10-31 17:52:24 +0300
committerDavid Woodhouse <David.Woodhouse@intel.com>2008-10-31 17:52:24 +0300
commitb27cf88e9592953ae292d05324887f2f44979433 (patch)
tree9f903a17a08801197127b479429ee2e304898799 /fs/jffs2/README.Locking
parentf04de505e3fa322728d1a851e08bf7060b117743 (diff)
downloadlinux-b27cf88e9592953ae292d05324887f2f44979433.tar.xz
[JFFS2] Fix lack of locking in thread_should_wake()
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> Cc: stable@kernel.org
Diffstat (limited to 'fs/jffs2/README.Locking')
0 files changed, 0 insertions, 0 deletions