From: syzbot <syzbot+f2bbbb592debc978d46d@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, baolin.wang@linux.alibaba.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] BUG: Bad rss-counter state (5)
Date: Fri, 14 Jun 2024 08:12:04 -0700 [thread overview]
Message-ID: <000000000000c2c1fd061adb09d1@google.com> (raw)
In-Reply-To: <0000000000007a211706185338b0@google.com>
syzbot has bisected this issue to:
commit 1c05047ad01693ad92bdf8347fad3b5c2b25e8bb
Author: Baolin Wang <baolin.wang@linux.alibaba.com>
Date: Tue Jun 4 10:17:45 2024 +0000
mm: memory: extend finish_fault() to support large folio
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=106e8e56980000
start commit: d35b2284e966 Add linux-next specific files for 20240607
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=126e8e56980000
console output: https://syzkaller.appspot.com/x/log.txt?x=146e8e56980000
kernel config: https://syzkaller.appspot.com/x/.config?x=d8bf5cd6bcca7343
dashboard link: https://syzkaller.appspot.com/bug?extid=f2bbbb592debc978d46d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17f57a36980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10a57696980000
Reported-by: syzbot+f2bbbb592debc978d46d@syzkaller.appspotmail.com
Fixes: 1c05047ad016 ("mm: memory: extend finish_fault() to support large folio")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-06-14 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 10:19 [syzbot] BUG: Bad rss-counter state (5) syzbot
2024-05-30 17:30 ` syzbot
2024-06-14 15:12 ` syzbot [this message]
2024-06-14 15:49 ` Baolin Wang
2024-06-14 15:49 ` syzbot
2024-06-14 15:50 ` Baolin Wang
2024-06-14 16:18 ` syzbot
2025-07-22 18:31 ` Forwarded: 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=000000000000c2c1fd061adb09d1@google.com \
--to=syzbot+f2bbbb592debc978d46d@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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.