On Sat, Aug 15 2020 at 01:37, Stephen Boyd wrote:
> Quoting Thomas Gleixner (2020-08-12 03:27:03)
>> or any other variant of insanity which makes the check claim that this
>> is statically initialized then you rightfully can keep the pieces :)
>
> Makes sense. Maybe this "technique" should be docum
Quoting Thomas Gleixner (2020-08-12 03:27:03)
> Stephen,
>
> Stephen Boyd writes:
> > Quoting Qianli Zhao (2020-08-11 22:14:14)
> >> +/** kernel/kthread **/
> >> +#define KWORK_ENTRY_STATIC ((void *) 0x600 + POISON_POINTER_DELTA)
> >
> > Is this related to the debugobjects cha
Stephen,
Stephen Boyd writes:
> Quoting Qianli Zhao (2020-08-11 22:14:14)
>> +/** kernel/kthread **/
>> +#define KWORK_ENTRY_STATIC ((void *) 0x600 + POISON_POINTER_DELTA)
>
> Is this related to the debugobjects change here? It looks like another
> version of list poison.
Yes
Qianli,
Qianli Zhao writes:
> Add debugobject support to track the life time of kthread_work
> which is used to detect reinitialization/free active object problems
> Add kthread_init_work_onstack/kthread_init_delayed_work_onstack for
> kthread onstack support
s/kthread/kthread_work/ ?
It would
Quoting Qianli Zhao (2020-08-11 22:14:14)
> @@ -115,7 +125,7 @@ struct kthread_delayed_work {
> }
>
> #define KTHREAD_WORK_INIT(work, fn){ \
> - .node = LIST_HEAD_INIT((work).node),\
> + .node = { .next = KWORK_ENT
From: Qianli Zhao
Add debugobject support to track the life time of kthread_work
which is used to detect reinitialization/free active object problems
Add kthread_init_work_onstack/kthread_init_delayed_work_onstack for
kthread onstack support
Signed-off-by: Qianli Zhao
---
I got an crash issue s
6 matches
Mail list logo
