From: syzbot <syzbot+17416257cb95200cba44@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, hannes@cmpxchg.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
riel@surriel.com, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] UBSAN: shift-out-of-bounds in try_to_shrink_lruvec
Date: Tue, 28 May 2024 18:54:02 -0700 [thread overview]
Message-ID: <0000000000005a9fbd06198e06b4@google.com> (raw)
In-Reply-To: <0000000000004d74b30619866a7f@google.com>
syzbot has bisected this issue to:
commit 6be5e186fd655df4b3ba267054de2eaaadc71340
Author: Johannes Weiner <hannes@cmpxchg.org>
Date: Tue May 14 20:26:41 2024 +0000
mm: vmscan: restore incremental cgroup iteration
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=179315c8980000
start commit: 6dc544b66971 Add linux-next specific files for 20240528
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=145315c8980000
console output: https://syzkaller.appspot.com/x/log.txt?x=105315c8980000
kernel config: https://syzkaller.appspot.com/x/.config?x=6a363b35598e573d
dashboard link: https://syzkaller.appspot.com/bug?extid=17416257cb95200cba44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11e41b72980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15f3d2d2980000
Reported-by: syzbot+17416257cb95200cba44@syzkaller.appspotmail.com
Fixes: 6be5e186fd65 ("mm: vmscan: restore incremental cgroup iteration")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-05-29 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 16:49 [syzbot] [mm?] UBSAN: shift-out-of-bounds in try_to_shrink_lruvec syzbot
2024-05-29 1:54 ` syzbot [this message]
2024-05-29 15:02 ` Shakeel Butt
2024-05-29 15:43 ` 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=0000000000005a9fbd06198e06b4@google.com \
--to=syzbot+17416257cb95200cba44@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@surriel.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--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 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.