Re: [PATCH] lockdep: fix oops in processing workqueue

[Dave Jones]

On Tue, May 15, 2012 at 08:10:48AM -0700, Tejun Heo wrote:
 > >From 4d82a1debbffec129cc387aafa8f40b7bbab3297 Mon Sep 17 00:00:00 2001
 > From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
 > Date: Tue, 15 May 2012 08:06:19 -0700
 > 
 > Under memory load, on x86_64, with lockdep enabled, the workqueue's
 > process_one_work() has been seen to oops in __lock_acquire(), barfing
 > on a 0xffffffff00000000 pointer in the lockdep_map's class_cache[].

can you elaborate what 'memory load' means here ?
I'm curious if I can add something to my fuzzing tool to shake out bugs like this.

	Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/