Re: [PATCH 3/3] spinlock_debug: panic on recursive lock spin_dump()

2016-02-01 Thread Sergey Senozhatsky
On (02/02/16 01:14), Sergey Senozhatsky wrote: > how about splitting ->owner_cpu 4 bytes as: > > | | > 1 byte spin bug recursion | 1 byte spin_dump recursion counter | 2 bytes > owner cpu > |

Re: [PATCH 3/3] spinlock_debug: panic on recursive lock spin_dump()

2016-02-01 Thread Sergey Senozhatsky
On (01/31/16 21:33), Sergey Senozhatsky wrote: > spin_dump() calls printk() which can attempt to reacquire the > 'buggy' lock (one of printk's lock, or console device driver lock, > etc.) and thus spin_dump() will recurse into itself. how about splitting ->owner_cpu 4 bytes as:

[PATCH 3/3] spinlock_debug: panic on recursive lock spin_dump()

2016-01-31 Thread Sergey Senozhatsky
spin_dump() calls printk() which can attempt to reacquire the 'buggy' lock (one of printk's lock, or console device driver lock, etc.) and thus spin_dump() will recursive into itself. Steal most significant bit of spin_lock->owner_cpu to keep there a mark that spin_dump() is in progress for that pa