From: syzbot <syzbot+ec972d37869318fc3ffb-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org>
To: akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org,
shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org,
songmuchun-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org,
syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
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-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
syzbot has bisected this issue to:
commit cca700a8e695fbe4a647e3a509ac513f05d5740a
Author: Muchun Song <songmuchun-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org>
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-Pl5Pbv+GP7P466ipTTIvnc23WoclnBCfAL8bYrjMMd8@public.gmane.org
Fixes: cca700a8e695 ("mm: lru: use lruvec lock to serialize memcg changes")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
WARNING: multiple messages have this Message-ID (diff)
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
next prev parent reply other threads:[~2022-06-25 6:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 13:49 [syzbot] WARNING in folio_lruvec_lock_irqsave syzbot
2022-06-22 13:49 ` syzbot
2022-06-23 2:58 ` syzbot
[not found] ` <0000000000004b03c805e2099bf0-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2022-06-22 15:33 ` Muchun Song
2022-06-22 15:33 ` Muchun Song
[not found] ` <YrM2XCwzu65cb81r-t1y1lxtqHnkkxugUQmjJ3WroNbXEc4rFQQ4Iyu8u01E@public.gmane.org>
2022-06-23 2:32 ` 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:52 ` Roman Gushchin
2022-06-25 6:00 ` syzbot [this message]
2022-06-25 6:00 ` 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=0000000000003ad3d705e23f66ae@google.com \
--to=syzbot+ec972d37869318fc3ffb-pl5pbv+gp7p466ipttivnc23woclnbcfal8byrjmmd8@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=roman.gushchin-fxUVXftIFDnyG1zEObXtfA@public.gmane.org \
--cc=shakeelb-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org \
--cc=songmuchun-EC8Uxl6Npydl57MIdRCFDg@public.gmane.org \
--cc=syzkaller-bugs-/JYPxA39Uh5TLH3MbocFFw@public.gmane.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.