From: syzbot <syzbot+8645fe63c4d22c8d27b8@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, liam.howlett@oracle.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, willy@infradead.org
Subject: Re: [syzbot] [mm?] WARNING: suspicious RCU usage in mas_walk (2)
Date: Tue, 25 Jul 2023 23:57:22 -0700 [thread overview]
Message-ID: <0000000000000aeb7f06015e5cbd@google.com> (raw)
In-Reply-To: <000000000000607ff905ffc8e477@google.com>
syzbot has bisected this issue to:
commit a52f58b34afe095ebc5823684eb264404dad6f7b
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Mon Jul 24 18:54:10 2023 +0000
mm: handle faults that merely update the accessed bit under the VMA lock
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1783585ea80000
start commit: [unknown]
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1443585ea80000
console output: https://syzkaller.appspot.com/x/log.txt?x=1043585ea80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f481ab36ce878b84
dashboard link: https://syzkaller.appspot.com/bug?extid=8645fe63c4d22c8d27b8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1697cec9a80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1566986ea80000
Reported-by: syzbot+8645fe63c4d22c8d27b8@syzkaller.appspotmail.com
Fixes: a52f58b34afe ("mm: handle faults that merely update the accessed bit under the VMA lock")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-07-26 6:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 3:12 [syzbot] [mm?] WARNING: suspicious RCU usage in mas_walk (2) syzbot
2023-07-06 16:53 ` Liam R. Howlett
2023-07-25 20:27 ` syzbot
2023-07-26 6:57 ` syzbot [this message]
2023-07-27 16:47 ` Liam R. Howlett
2023-07-27 17:22 ` Suren Baghdasaryan
2023-07-27 17:59 ` Jann Horn
2023-07-27 18:12 ` Liam R. Howlett
2023-07-27 18:17 ` Matthew Wilcox
2023-07-27 18:31 ` Suren Baghdasaryan
2023-07-27 18:46 ` Matthew Wilcox
2023-07-27 19:20 ` Jann Horn
2023-07-27 20:08 ` Matthew Wilcox
2023-07-27 18:50 ` Matthew Wilcox
2023-07-27 18:50 ` syzbot
2023-07-27 18:52 ` Matthew Wilcox
2023-07-27 18:53 ` syzbot
2023-07-27 18:54 ` Matthew Wilcox
2023-07-27 19:12 ` Aleksandr Nogikh
2023-07-27 18:56 ` Matthew Wilcox
2023-07-27 19:17 ` syzbot
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=0000000000000aeb7f06015e5cbd@google.com \
--to=syzbot+8645fe63c4d22c8d27b8@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willy@infradead.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 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.