)]}' { "log": [ { "commit": "632ee200130899252508c478ad0e808222573fbc", "tree": "e3f44ca9daf2a2da2186419f703bc9cec8faa058", "parents": [ "996de8c6fe95c5a9fc524241cc8f142ef0605d3d" ], "author": { "name": "Paul E. McKenney", "email": "paulmck@linux.vnet.ibm.com", "time": "Mon Feb 22 17:04:45 2010 -0800" }, "committer": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Thu Feb 25 09:40:59 2010 +0100" }, "message": "rcu: Introduce lockdep-based checking to RCU read-side primitives\n\nInspection is proving insufficient to catch all RCU misuses,\nwhich is understandable given that rcu_dereference() might be\nprotected by any of four different flavors of RCU (RCU, RCU-bh,\nRCU-sched, and SRCU), and might also/instead be protected by any\nof a number of locking primitives. It is therefore time to\nenlist the aid of lockdep.\n\nThis set of patches is inspired by earlier work by Peter\nZijlstra and Thomas Gleixner, and takes the following approach:\n\no\tSet up separate lockdep classes for RCU, RCU-bh, and RCU-sched.\n\no\tSet up separate lockdep classes for each instance of SRCU.\n\no\tCreate primitives that check for being in an RCU read-side\n\tcritical section. These return exact answers if lockdep is\n\tfully enabled, but if unsure, report being in an RCU read-side\n\tcritical section. (We want to avoid false positives!)\n\tThe primitives are:\n\n\tFor RCU: rcu_read_lock_held(void)\n\n\tFor RCU-bh: rcu_read_lock_bh_held(void)\n\n\tFor RCU-sched: rcu_read_lock_sched_held(void)\n\n\tFor SRCU: srcu_read_lock_held(struct srcu_struct *sp)\n\no\tAdd rcu_dereference_check(), which takes a second argument\n\tin which one places a boolean expression based on the above\n\tprimitives and/or lockdep_is_held().\n\no\tA new kernel configuration parameter, CONFIG_PROVE_RCU, enables\n\trcu_dereference_check(). This depends on CONFIG_PROVE_LOCKING,\n\tand should be quite helpful during the transition period while\n\tCONFIG_PROVE_RCU-unaware patches are in flight.\n\nThe existing rcu_dereference() primitive does no checking, but\nupcoming patches will change that.\n\nSigned-off-by: Paul E. McKenney \u003cpaulmck@linux.vnet.ibm.com\u003e\nCc: laijs@cn.fujitsu.com\nCc: dipankar@in.ibm.com\nCc: mathieu.desnoyers@polymtl.ca\nCc: josh@joshtriplett.org\nCc: dvhltc@us.ibm.com\nCc: niv@us.ibm.com\nCc: peterz@infradead.org\nCc: rostedt@goodmis.org\nCc: Valdis.Kletnieks@vt.edu\nCc: dhowells@redhat.com\nLKML-Reference: \u003c1266887105-1528-1-git-send-email-paulmck@linux.vnet.ibm.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "9eeba6138cefc0435695463ddadb0d95e0a6bcd2", "tree": "daba646e5ddd27132e9679aa3eabec389bf4722e", "parents": [ "066123a535927b3f17cac2305258cc71abdb0d92" ], "author": { "name": "Frederic Weisbecker", "email": "fweisbec@gmail.com", "time": "Sat Apr 11 03:17:17 2009 +0200" }, "committer": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Sun Apr 12 16:10:51 2009 +0200" }, "message": "lockdep: warn about lockdep disabling after kernel taint\n\nImpact: provide useful missing info for developers\n\nKernel taint can occur in several situations such as warnings,\nload of prorietary or staging modules, bad page, etc...\n\nBut when such taint happens, a developer might still be working on\nthe kernel, expecting that lockdep is still enabled. But a taint\ndisables lockdep without ever warning about it.\nSuch a kernel behaviour doesn\u0027t really help for kernel development.\n\nThis patch adds this missing warning.\n\nSince the taint is done most of the time after the main message that\nexplain the real source issue, it seems safe to warn about it inside\nadd_taint() so that it appears at last, without hurting the main\ninformation.\n\nv2: Use a generic helper to disable lockdep instead of an\n open coded xchg().\n\nSigned-off-by: Frederic Weisbecker \u003cfweisbec@gmail.com\u003e\nCc: Peter Zijlstra \u003cpeterz@infradead.org\u003e\nLKML-Reference: \u003c1239412638-6739-1-git-send-email-fweisbec@gmail.com\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "e0fdace10e75dac67d906213b780ff1b1a4cc360", "tree": "ca0ab78da383bfe44512bc33a1431d1a9dc4537f", "parents": [ "419ca3f13532793b81aff09f80c60af3eacbb43d" ], "author": { "name": "David Miller", "email": "davem@davemloft.net", "time": "Fri Aug 01 01:11:22 2008 -0700" }, "committer": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Fri Aug 01 10:46:43 2008 +0200" }, "message": "debug_locks: set oops_in_progress if we will log messages.\n\nOtherwise lock debugging messages on runqueue locks can deadlock the\nsystem due to the wakeups performed by printk().\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\n" }, { "commit": "9a11b49a805665e13a56aa067afaf81d43ec1514", "tree": "bf499956e3f67d1211d68ab1e2eb76645f453dfb", "parents": [ "fb7e42413a098cc45b3adf858da290033af62bae" ], "author": { "name": "Ingo Molnar", "email": "mingo@elte.hu", "time": "Mon Jul 03 00:24:33 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jul 03 15:27:01 2006 -0700" }, "message": "[PATCH] lockdep: better lock debugging\n\nGeneric lock debugging:\n\n - generalized lock debugging framework. For example, a bug in one lock\n subsystem turns off debugging in all lock subsystems.\n\n - got rid of the caller address passing (__IP__/__IP_DECL__/etc.) from\n the mutex/rtmutex debugging code: it caused way too much prototype\n hackery, and lockdep will give the same information anyway.\n\n - ability to do silent tests\n\n - check lock freeing in vfree too.\n\n - more finegrained debugging options, to allow distributions to\n turn off more expensive debugging features.\n\nThere\u0027s no separate \u0027held mutexes\u0027 list anymore - but there\u0027s a \u0027held locks\u0027\nstack within lockdep, which unifies deadlock detection across all lock\nclasses. (this is independent of the lockdep validation stuff - lockdep first\nchecks whether we are holding a lock already)\n\nHere are the current debugging options:\n\nCONFIG_DEBUG_MUTEXES\u003dy\nCONFIG_DEBUG_LOCK_ALLOC\u003dy\n\nwhich do:\n\n config DEBUG_MUTEXES\n bool \"Mutex debugging, basic checks\"\n\n config DEBUG_LOCK_ALLOC\n bool \"Detect incorrect freeing of live mutexes\"\n\nSigned-off-by: Ingo Molnar \u003cmingo@elte.hu\u003e\nSigned-off-by: Arjan van de Ven \u003carjan@linux.intel.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" } ] }