From: Petr Mladek <pmladek@suse.com>
To: wzs <wangzhengshu39@gmail.com>
Cc: dianders@chromium.org, tglx@linutronix.de,
liusong@linux.alibaba.com, akpm@linux-foundation.org,
kernelfans@gmail.com, deller@gmx.de, npiggin@gmail.com,
tsbogend@alpha.franken.de, James.Bottomley@hansenpartnership.com,
jan.kiszka@siemens.com, linux-kernel@vger.kernel.org,
linux-mips@vger.kernel.org, linux-parisc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, yaoma@linux.alibaba.com
Subject: Re: watchdog: BUG: soft lockup
Date: Thu, 2 Jan 2025 17:10:33 +0100 [thread overview]
Message-ID: <Z3a6eQHwjRdwnDXp@pathway.suse.cz> (raw)
In-Reply-To: <CAGXGE_JWtMo8Qs=hsH=NULkDRFoYKYorKHACpqvqpYiO3am8eQ@mail.gmail.com>
On Mon 2024-12-23 14:32:11, wzs wrote:
> Hello,
> when fuzzing the Linux kernel,
> I triggered many "watch: BUG: soft lockup" warnings.
> I am not sure whether this is an issue with the kernel or with the
> fuzzing program I ran.
> (The same fuzzing program, when tested on kernel versions from
> Linux-6.7.0 to 6.12.0, triggers the 'watchdog: BUG: soft lockup'
> warning on some versions, while others do not. Linux 6.12.0 is the
> latest stable release where this error occurs.)
I am not sure if I understand the above correctly.
Did you test also kernel versions older than 6.7.0 or newer then 6.12.0?
Was the result random? Like for example, did you saw the problem
on 6.7.0 and 6.12.0 but not on 6.9.0?
Did you try to run the test more times with the same version of the
kernel? Was it reproducible?
I guess that the problem is in all versions but it is not 100%
reproducible. So that the softlockup happens or does not happen by chance.
> The bug information I provided below is from the Linux-6.12.0 kernel.
> If you need bug information from other versions, I would be happy to provide it.
>
> kernel config :https://pastebin.com/i4LPXNAN
> console output :https://pastebin.com/uKVpvJ78
It would be great to see at least three logs. It might help to find
a common pattern.
Also it would be great to provide a full log if possible. Or at least
the boot part and few more lines before the crash.
Best Regards,
Petr
next prev parent reply other threads:[~2025-01-02 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 6:32 watchdog: BUG: soft lockup wzs
2025-01-02 16:10 ` Petr Mladek [this message]
2025-01-08 17:27 ` Doug Anderson
2025-01-13 8:27 ` wzs
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=Z3a6eQHwjRdwnDXp@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=deller@gmx.de \
--cc=dianders@chromium.org \
--cc=jan.kiszka@siemens.com \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=liusong@linux.alibaba.com \
--cc=npiggin@gmail.com \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=wangzhengshu39@gmail.com \
--cc=yaoma@linux.alibaba.com \
/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;
as well as URLs for NNTP newsgroup(s).