From: Jiaqi Yan <jiaqiyan@google.com>
To: syzbot <syzbot+3d4aa0d3e784b29b1520@syzkaller.appspotmail.com>
Cc: akpm@linux-foundation.org, hughd@google.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
shy828301@gmail.com, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [mm?] WARNING in shmem_evict_inode
Date: Fri, 5 May 2023 20:02:13 -0700 [thread overview]
Message-ID: <CACw3F53T=bbn6f6db_T_5=udLq-cvChYALhmmpQ1QOkjH-7gpg@mail.gmail.com> (raw)
In-Reply-To: <00000000000014678c05faf51958@google.com>
It seems commit 12904d953364 caused the WARNING when MADV_COLLAPSE on
shmem memory, but right now the root cause is still unclear to me
after some digging. Will keep digging and/or try to repro over the
weekend.
On Fri, May 5, 2023 at 9:51 AM syzbot
<syzbot+3d4aa0d3e784b29b1520@syzkaller.appspotmail.com> wrote:
>
> syzbot has bisected this issue to:
>
> commit 12904d953364e3bd21789a45137bf90df7cc78ee
> Author: Jiaqi Yan <jiaqiyan@google.com>
> Date: Wed Mar 29 15:11:21 2023 +0000
>
> mm/khugepaged: recover from poisoned file-backed memory
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14f67032280000
> start commit: 3c4aa4434377 Merge tag 'ceph-for-6.4-rc1' of https://githu..
> git tree: upstream
> final oops: https://syzkaller.appspot.com/x/report.txt?x=16f67032280000
> console output: https://syzkaller.appspot.com/x/log.txt?x=12f67032280000
> kernel config: https://syzkaller.appspot.com/x/.config?x=c1d541e02d3faec
> dashboard link: https://syzkaller.appspot.com/bug?extid=3d4aa0d3e784b29b1520
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14d1973c280000
>
> Reported-by: syzbot+3d4aa0d3e784b29b1520@syzkaller.appspotmail.com
> Fixes: 12904d953364 ("mm/khugepaged: recover from poisoned file-backed memory")
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-05-06 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00000000000016552c05f1d7e734@google.com>
2023-05-05 10:43 ` syzbot
2023-05-05 16:51 ` syzbot
2023-05-06 3:02 ` Jiaqi Yan [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='CACw3F53T=bbn6f6db_T_5=udLq-cvChYALhmmpQ1QOkjH-7gpg@mail.gmail.com' \
--to=jiaqiyan@google.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shy828301@gmail.com \
--cc=syzbot+3d4aa0d3e784b29b1520@syzkaller.appspotmail.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