[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250214164556.GA13743@willie-the-truck>
Date: Fri, 14 Feb 2025 16:45:57 +0000
From: Will Deacon <will@...nel.org>
To: Tejun Heo <tj@...nel.org>
Cc: syzbot <syzbot+e13e654d315d4da1277c@...kaller.appspotmail.com>,
catalin.marinas@....com, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com,
maz@...nel.org, mark.rutland@....com, richard.xnu.clark@...il.com,
jiangshanlai@...il.com, marcel@...tmann.org,
johan.hedberg@...il.com, luiz.dentz@...il.com,
linux-bluetooth@...r.kernel.org
Subject: Re: [syzbot] [arm?] WARNING in delayed_work_timer_fn
On Tue, Feb 11, 2025 at 10:59:30AM -1000, Tejun Heo wrote:
> On Tue, Feb 11, 2025 at 11:10:46AM +0000, Will Deacon wrote:
> > Given that this seems to explode a few times a month, I wonder if it's
> > worth adding some instrumentation to e.g. dump the name of the workqueue?
>
> It's usually most useful to print out the work function when identifying the
> culprit. I'd be happy to take the patch.
Thanks, Tejun. I sent a patch adding some more diagnostics:
https://lore.kernel.org/r/20250214164349.13694-1-will@kernel.org
Will
Powered by blists - more mailing lists