From: syzbot <syzbot+2403e3909382fbdeaf6c@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, kent.overstreet@linux.dev,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com, tangyouling@kylinos.cn
Subject: Re: [syzbot] [mm?] BUG: unable to handle kernel paging request in list_lru_add
Date: Fri, 12 Jul 2024 18:14:02 -0700 [thread overview]
Message-ID: <000000000000208785061d16b6f0@google.com> (raw)
In-Reply-To: <0000000000006d415806048a9aee@google.com>
syzbot has bisected this issue to:
commit 86d81ec5f5f05846c7c6e48ffb964b24cba2e669
Author: Youling Tang <tangyouling@kylinos.cn>
Date: Wed Jul 3 07:09:55 2024 +0000
bcachefs: Mark bch_inode_info as SLAB_ACCOUNT
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=113f4bed980000
start commit: 43db1e03c086 Merge tag 'for-6.10/dm-fixes-2' of git://git...
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=133f4bed980000
console output: https://syzkaller.appspot.com/x/log.txt?x=153f4bed980000
kernel config: https://syzkaller.appspot.com/x/.config?x=42a432cfd0e579e0
dashboard link: https://syzkaller.appspot.com/bug?extid=2403e3909382fbdeaf6c
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141c864e980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12b1da7e980000
Reported-by: syzbot+2403e3909382fbdeaf6c@syzkaller.appspotmail.com
Fixes: 86d81ec5f5f0 ("bcachefs: Mark bch_inode_info as SLAB_ACCOUNT")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-07-13 1:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 16:00 [syzbot] [mm?] BUG: unable to handle kernel paging request in list_lru_add syzbot
2023-12-27 15:50 ` syzbot
2024-07-12 17:11 ` syzbot
2024-07-13 1:14 ` syzbot [this message]
2024-08-22 1:51 ` syzbot
2024-08-22 1:54 ` Kent Overstreet
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=000000000000208785061d16b6f0@google.com \
--to=syzbot+2403e3909382fbdeaf6c@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tangyouling@kylinos.cn \
/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).