Messages in this thread | | | Date | Thu, 10 Dec 2015 10:02:51 +0100 | From | Peter Zijlstra <> | Subject | Re: use-after-free in __perf_install_in_context |
| |
On Wed, Dec 09, 2015 at 07:54:35PM -0800, Alexei Starovoitov wrote: > Freeing memory is a requirement regardless. > Even when kernel running with kasan, there must be a way to stop > stack collection and free that memory. > You cannot treat kernel as your test program or 'device under test'.
Relax, that is exactly what lockdep does. It cannot dynamically allocate things because allocators use lock etc..
Its fine to build up state for debug bits, esp. if its bounded, like the number of unique callchains.
| |