From: syzbot <syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, chao@kernel.org,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
sfr@canb.auug.org.au, songmuchun@bytedance.com,
syzkaller-bugs@googlegroups.com, xiang@kernel.org
Subject: Re: [syzbot] WARNING: kobject bug in erofs_unregister_sysfs
Date: Fri, 18 Mar 2022 15:33:07 -0700 [thread overview]
Message-ID: <00000000000009cf1e05da85bb31@google.com> (raw)
In-Reply-To: <000000000000dda2f905da80c934@google.com>
syzbot has bisected this issue to:
commit 2768c206f2c3e95c0e5cf2e7f846103fda7cd429
Author: Muchun Song <songmuchun@bytedance.com>
Date: Thu Mar 3 01:15:36 2022 +0000
mm: list_lru: allocate list_lru_one only when needed
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1495694d700000
start commit: 91265a6da44d Add linux-next specific files for 20220303
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=1695694d700000
console output: https://syzkaller.appspot.com/x/log.txt?x=1295694d700000
kernel config: https://syzkaller.appspot.com/x/.config?x=617f79440a35673a
dashboard link: https://syzkaller.appspot.com/bug?extid=f05ba4652c0471416eaf
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=137f17d9700000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=114ebabd700000
Reported-by: syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com
Fixes: 2768c206f2c3 ("mm: list_lru: allocate list_lru_one only when needed")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2022-03-18 22:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 16:39 [syzbot] WARNING: kobject bug in erofs_unregister_sysfs syzbot
2022-03-18 18:02 ` Gao Xiang
2022-03-18 18:52 ` syzbot
2022-03-18 22:33 ` syzbot [this message]
2022-03-19 2:19 ` Muchun Song
2022-03-19 3:45 ` Gao Xiang
2022-03-20 4:19 ` Dongliang Mu
2022-03-21 6:55 ` Dmitry Vyukov
2022-03-23 1:54 ` Gao Xiang
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=00000000000009cf1e05da85bb31@google.com \
--to=syzbot+f05ba4652c0471416eaf@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=chao@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=songmuchun@bytedance.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiang@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox