From: syzbot <syzbot+ec972d37869318fc3ffb@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, cgroups@vger.kernel.org,
hannes@cmpxchg.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mhocko@kernel.org, roman.gushchin@linux.dev,
shakeelb@google.com, songmuchun@bytedance.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in folio_lruvec_lock_irqsave
Date: Fri, 24 Jun 2022 23:00:09 -0700 [thread overview]
Message-ID: <0000000000003ad3d705e23f66ae@google.com> (raw)
In-Reply-To: <0000000000004b03c805e2099bf0@google.com>
syzbot has bisected this issue to:
commit cca700a8e695fbe4a647e3a509ac513f05d5740a
Author: Muchun Song <songmuchun@bytedance.com>
Date: Tue Jun 21 12:56:58 2022 +0000
mm: lru: use lruvec lock to serialize memcg changes
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15abaf18080000
start commit: ac0ba5454ca8 Add linux-next specific files for 20220622
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=17abaf18080000
console output: https://syzkaller.appspot.com/x/log.txt?x=13abaf18080000
kernel config: https://syzkaller.appspot.com/x/.config?x=12809dacb9e7c5e0
dashboard link: https://syzkaller.appspot.com/bug?extid=ec972d37869318fc3ffb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12d0f470080000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1145df0ff00000
Reported-by: syzbot+ec972d37869318fc3ffb@syzkaller.appspotmail.com
Fixes: cca700a8e695 ("mm: lru: use lruvec lock to serialize memcg changes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2022-06-25 6:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 13:49 syzbot
2022-06-22 15:33 ` Muchun Song
2022-06-23 2:32 ` Muchun Song
2022-06-23 2:59 ` Roman Gushchin
2022-06-23 3:49 ` Muchun Song
2022-06-23 2:52 ` Roman Gushchin
2022-06-23 2:58 ` syzbot
2022-06-25 6:00 ` 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=0000000000003ad3d705e23f66ae@google.com \
--to=syzbot+ec972d37869318fc3ffb@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=songmuchun@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox