Re: [PATCH] kdb: Make memory allocations more robust

On Fri, Jan 22, 2021 at 03:08:31PM +0530, Sumit Garg wrote: > Currently kdb uses in_interrupt() to determine whether it's library > code has been called from the kgdb trap handler or from a saner calling > context such as driver init. This approach is broken because > in_interrupt() alone isn't

Re: [PATCH] kdb: Make memory allocations more robust

On Fri, 22 Jan 2021 at 15:18, Daniel Thompson wrote: > > On Fri, Jan 22, 2021 at 03:08:31PM +0530, Sumit Garg wrote: > > Currently kdb uses in_interrupt() to determine whether it's library > > code has been called from the kgdb trap handler or from a saner calling > > context such as driver init.

[PATCH] kdb: Make memory allocations more robust

Currently kdb uses in_interrupt() to determine whether it's library code has been called from the kgdb trap handler or from a saner calling context such as driver init. This approach is broken because in_interrupt() alone isn't able to determine kgdb trap handler entry via normal task context such