From: Yu Zhao <yuzhao@google.com>
To: Hillf Danton <hdanton@sina.com>, Dmitry Vyukov <dvyukov@google.com>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [syzbot] [nilfs2?] INFO: task hung in nilfs_segctor_thread
Date: Tue, 14 Feb 2023 23:02:02 -0700 [thread overview]
Message-ID: <CAOUHufYzJoh=Pvican+c8E5-5vyv_TuVaa27nDKXw3CLR=ca5A@mail.gmail.com> (raw)
In-Reply-To: <20230215015231.3646-1-hdanton@sina.com>
On Tue, Feb 14, 2023 at 6:52 PM Hillf Danton <hdanton@sina.com> wrote:
>
> On Tue, 14 Feb 2023 00:14:42 -0800
> > syzbot has found a reproducer for the following issue on:
> >
> > HEAD commit: f6feea56f66d Merge tag 'mm-hotfixes-stable-2023-02-13-13-5..
> > git tree: upstream
> > console+strace: https://syzkaller.appspot.com/x/log.txt?x=165ee62b480000
> > kernel config: https://syzkaller.appspot.com/x/.config?x=42ba4da8e1e6af9f
> > dashboard link: https://syzkaller.appspot.com/bug?extid=f0c4082ce5ebebdac63b
> > compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
> > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14ba7207480000
> > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15fd30d0c80000
> >
> > Downloadable assets:
> > disk image: https://storage.googleapis.com/syzbot-assets/1ae0143f08d5/disk-f6feea56.raw.xz
> > vmlinux: https://storage.googleapis.com/syzbot-assets/18b8a23fa0cb/vmlinux-f6feea56.xz
> > kernel image: https://storage.googleapis.com/syzbot-assets/d915f4c5c8c0/bzImage-f6feea56.xz
> > mounted in repro: https://storage.googleapis.com/syzbot-assets/1acd3b288433/mount_0.gz
> >
> > folio_mark_accessed+0x51c/0xf00 mm/swap.c:515
>
> Syzbot was launched without MGLRU enabled [1].
> Dmitry could you turn it on by default?
Thanks for the heads up!
(I should have followed up with Dmitry earlier... doing it now.)
next prev parent reply other threads:[~2023-02-15 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0000000000004e1dfa05f4a48e6b@google.com>
2023-02-15 1:52 ` Hillf Danton
2023-02-15 6:02 ` Yu Zhao [this message]
2023-02-15 8:52 ` Dmitry Vyukov
2024-05-12 3:33 naseriamin080
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='CAOUHufYzJoh=Pvican+c8E5-5vyv_TuVaa27nDKXw3CLR=ca5A@mail.gmail.com' \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox