On 11/16, Roland McGrath wrote: > > > Yes it does. I am almost sure the bug should be trivial, but > > somehow can't find find it. Just fyi, to ensure this is connected > > to utrace-indirect I applied the hack below and the bug goes away. > > Does s/kmem_cache_zalloc/kzalloc/ really have anything to do with it?
No, I think it doesn't. I did this s/kmem_cache_zalloc/kzalloc/ change because I am not sure copy_process() during the boot stage can safely use utrace_cachep which is initialized by module_init(). Oleg.
