From: syzbot <syzbot+79fcba037b6df73756d3@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hughd@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, postmaster@duagon.onmicrosoft.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING: suspicious RCU usage in mas_walk (3)
Date: Tue, 24 Oct 2023 17:07:32 -0700 [thread overview]
Message-ID: <000000000000e6dbc706087f3df8@google.com> (raw)
In-Reply-To: <000000000000985ef90607610b0a@google.com>
syzbot has bisected this issue to:
commit edd33b8807a1fa6268a71758bf38de0b4adf2e70
Author: Hugh Dickins <hughd@google.com>
Date: Tue Oct 3 09:29:00 2023 +0000
mempolicy: migration attempt to match interleave nodes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13d353cb680000
start commit: e8361b005d7c Add linux-next specific files for 20231023
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=103353cb680000
console output: https://syzkaller.appspot.com/x/log.txt?x=17d353cb680000
kernel config: https://syzkaller.appspot.com/x/.config?x=39bda8753f457952
dashboard link: https://syzkaller.appspot.com/bug?extid=79fcba037b6df73756d3
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13714705680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1236430b680000
Reported-by: syzbot+79fcba037b6df73756d3@syzkaller.appspotmail.com
Fixes: edd33b8807a1 ("mempolicy: migration attempt to match interleave nodes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-10-25 0:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 18:40 [syzbot] [mm?] WARNING: suspicious RCU usage in mas_walk (3) syzbot
2023-10-23 17:24 ` syzbot
2023-10-23 17:55 ` Liam R. Howlett
2023-10-23 20:21 ` Hugh Dickins
2023-10-24 9:31 ` syzbot
2023-10-25 0:07 ` 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=000000000000e6dbc706087f3df8@google.com \
--to=syzbot+79fcba037b6df73756d3@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=postmaster@duagon.onmicrosoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.