On Mon, Aug 04, 2008 at 04:32:12PM +0200, Peter Zijlstra wrote: > On Mon, 2008-08-04 at 07:26 -0700, Roland Dreier wrote: > > > No more than 48 locks (mutexes, rwlocks, spinlock, RCU, everything > > > covered by lockdep) held by any one code-path; including nested > > > interrupt contexts. > > > > Does that mean that something like the new mm_take_all_locks() operation > > is going to explode if someone tries to use it with lockdep on? > > Gah - yes, clearly nobody tried this.. :-/ > > Just looking at the code it will not only run into this limit, but it > would warn about recursion on the second file/anon vma due to utter lack > of annotation. > > Why are people still developing without lockdep? More puzzling, is why hasn't this triggered in the Fedora rawhide kernels, which do have lockdep enabled. Dave -- http://www.codemonkey.org.uk --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Srivatsa Vaddagiri | containers (was Re: -mm merge plans for 2.6.23) |
| Benjamin Herrenschmidt | Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway |
git: | |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Patrick McHardy | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 6/7] [CCID-2/3]: Fix sparse warnings |
