[lkml]   [2022]   [Jun]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: re. Spurious wakeup on a newly created kthread
On Mon 27-06-22 17:21:12, Tejun Heo wrote:
> Hello, Michal.
> On Mon, Jun 27, 2022 at 10:07:22AM +0200, Michal Hocko wrote:
> > So if somebody has woken up our thread from inside kthread() then it
> > doesn't have that pointer on the stack and I couldn't it find elsewhere
> > either. Maybe somebody has an idea where to look at.
> One way could be bpftrace'ing or printking __wake_up_common() and
> friends to dump backtrace if it's trying to wake a kthread whose comm
> starts with kworker/ and doesn't have (struct worker
> *)kthread_data(task)->pool set.

I am afraid I won't have a chance for a runtime debugging. All I have at
this stage is a crash dump.
Michal Hocko

 \ /
  Last update: 2022-06-27 12:19    [W:0.080 / U:4.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site