From: Tejun Heo <tj@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: syzbot <syzbot+e13e654d315d4da1277c@syzkaller.appspotmail.com>,
catalin.marinas@arm.com, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
maz@kernel.org, mark.rutland@arm.com,
richard.xnu.clark@gmail.com, jiangshanlai@gmail.com,
marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org
Subject: Re: [syzbot] [arm?] WARNING in delayed_work_timer_fn
Date: Tue, 11 Feb 2025 10:59:30 -1000 [thread overview]
Message-ID: <Z6u6MgaJWMpjCn4O@slm.duckdns.org> (raw)
In-Reply-To: <20250211111045.GA8885@willie-the-truck>
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
next prev parent reply other threads:[~2025-02-11 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000046efb605fec3def0@google.com>
2024-12-13 12:30 ` [syzbot] [arm?] WARNING in delayed_work_timer_fn syzbot
2025-02-11 11:10 ` Will Deacon
2025-02-11 20:59 ` Tejun Heo [this message]
2025-02-14 16:45 ` Will Deacon
2025-03-13 19:30 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Z6u6MgaJWMpjCn4O@slm.duckdns.org \
--to=tj@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=jiangshanlai@gmail.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=richard.xnu.clark@gmail.com \
--cc=syzbot+e13e654d315d4da1277c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox