Re: [PATCH 0/2] locking/lockdep: Track number of zapped classes & report abuse

2018-12-05 Thread Waiman Long
On 11/30/2018 09:38 AM, Waiman Long wrote: > On 11/29/2018 05:48 PM, Peter Zijlstra wrote: >> On Thu, Nov 29, 2018 at 05:41:35PM -0500, Waiman Long wrote: >>> When a kernel module is repeatedly load and unload, it will eventually >>> exhaust the lockdep entries resulting in a bug message. This is a

Re: [PATCH 0/2] locking/lockdep: Track number of zapped classes & report abuse

2018-11-30 Thread Waiman Long
On 11/29/2018 05:48 PM, Peter Zijlstra wrote: > On Thu, Nov 29, 2018 at 05:41:35PM -0500, Waiman Long wrote: >> When a kernel module is repeatedly load and unload, it will eventually >> exhaust the lockdep entries resulting in a bug message. This is a use >> case that the current lockdep code canno

Re: [PATCH 0/2] locking/lockdep: Track number of zapped classes & report abuse

2018-11-29 Thread Peter Zijlstra
On Thu, Nov 29, 2018 at 05:41:35PM -0500, Waiman Long wrote: > When a kernel module is repeatedly load and unload, it will eventually > exhaust the lockdep entries resulting in a bug message. This is a use > case that the current lockdep code cannot support. > > This patchset tracks the number of

[PATCH 0/2] locking/lockdep: Track number of zapped classes & report abuse

2018-11-29 Thread Waiman Long
When a kernel module is repeatedly load and unload, it will eventually exhaust the lockdep entries resulting in a bug message. This is a use case that the current lockdep code cannot support. This patchset tracks the number of zapped classes and print a warning if too many lockdep entries are wast