From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+0bef82da8b7dca7e5869@syzkaller.appspotmail.com>,
akpm@linux-foundation.org, syzkaller-bugs@googlegroups.com,
Koichiro Den <koichiro.den@canonical.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [syzbot] [mm?] upstream test error: WARNING in enable_work
Date: Fri, 10 Jan 2025 21:06:36 +0900 [thread overview]
Message-ID: <386a0baa-be4e-41f0-b38f-3be35285acd9@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <678033fe.050a0220.25a300.01ce.GAE@google.com>
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/mm/vmstat.c?id=adcfb264c3ed51fbbf5068ddf10d309a63683868
looks like the cause of this problem.
On 2025/01/10 5:39, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 9d89551994a4 Linux 6.13-rc6
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1180b9c4580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=10cb4f23d3e0f104
> dashboard link: https://syzkaller.appspot.com/bug?extid=0bef82da8b7dca7e5869
> compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
>
> Downloadable assets:
> disk image: https://storage.googleapis.com/syzbot-assets/ac26b8628463/disk-9d895519.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/05387975b936/vmlinux-9d895519.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/c28b69047c4b/bzImage-9d895519.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+0bef82da8b7dca7e5869@syzkaller.appspotmail.com
prev parent reply other threads:[~2025-01-10 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 20:39 syzbot
2025-01-10 12:06 ` Tetsuo Handa [this message]
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=386a0baa-be4e-41f0-b38f-3be35285acd9@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=koichiro.den@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzbot+0bef82da8b7dca7e5869@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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