From: syzbot <syzbot+c391aebb8e8e8cd95c55@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, kasan-dev@googlegroups.com,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mcgrof@kernel.org, mhiramat@kernel.org,
mhocko@suse.com, mike.kravetz@oracle.com, muchun.song@linux.dev,
syzkaller-bugs@googlegroups.com, torvalds@linux-foundation.org,
vbabka@suse.cz
Subject: Re: [syzbot] [mm?] INFO: task hung in hugetlb_wp
Date: Fri, 11 Oct 2024 08:17:02 -0700 [thread overview]
Message-ID: <6709416e.050a0220.4cbc0.000b.GAE@google.com> (raw)
In-Reply-To: <0000000000005d16fe061fcaf338@google.com>
syzbot has bisected this issue to:
commit 3db978d480e2843979a2b56f2f7da726f2b295b2
Author: Vlastimil Babka <vbabka@suse.cz>
Date: Mon Jun 8 04:40:24 2020 +0000
kernel/sysctl: support setting sysctl parameters from kernel command line
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14c7f380580000
start commit: b983b271662b misc: sgi-gru: Don't disable preemption in GR..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16c7f380580000
console output: https://syzkaller.appspot.com/x/log.txt?x=12c7f380580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fb6ea01107fa96bd
dashboard link: https://syzkaller.appspot.com/bug?extid=c391aebb8e8e8cd95c55
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=118c6fd0580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b6a040580000
Reported-by: syzbot+c391aebb8e8e8cd95c55@syzkaller.appspotmail.com
Fixes: 3db978d480e2 ("kernel/sysctl: support setting sysctl parameters from kernel command line")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2024-10-11 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 11:06 [syzbot] [kasan?] [mm?] INFO: task hung in hugetlb_wp syzbot
2024-10-10 9:46 ` [syzbot] " syzbot
2024-10-11 15:17 ` syzbot [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=6709416e.050a0220.4cbc0.000b.GAE@google.com \
--to=syzbot+c391aebb8e8e8cd95c55@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=kasan-dev@googlegroups.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=muchun.song@linux.dev \
--cc=syzkaller-bugs@googlegroups.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
/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