From: Dmitry Vyukov <dvyukov@google.com>
To: Yu Zhao <yuzhao@google.com>
Cc: Hillf Danton <hdanton@sina.com>,
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: Wed, 15 Feb 2023 09:52:51 +0100 [thread overview]
Message-ID: <CACT4Y+bKBHus8oe5cMtSfdtG9mMGZGUywA1k_UYCSrwfXWv44A@mail.gmail.com> (raw)
In-Reply-To: <CAOUHufYzJoh=Pvican+c8E5-5vyv_TuVaa27nDKXw3CLR=ca5A@mail.gmail.com>
On Wed, 15 Feb 2023 at 07:02, Yu Zhao <yuzhao@google.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.)
Here is configs change (speak up if you don't agree with something):
https://github.com/google/syzkaller/pull/3683/commits/e3c95b410e328b52fef013a8071e47c6c278b1ed
next prev parent reply other threads:[~2023-02-15 8:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 20:32 [syzbot] INFO: task hung in nilfs_segctor_thread syzbot
2022-11-09 20:32 ` syzbot
2023-02-14 8:14 ` [syzbot] [nilfs2?] " syzbot
2023-02-14 8:14 ` syzbot
2023-02-14 9:11 ` Ryusuke Konishi
2023-02-14 9:11 ` Ryusuke Konishi
2023-02-14 22:40 ` [PATCH] nilfs2: fix underflow in second superblock position calculations Ryusuke Konishi
2023-02-14 22:40 ` Ryusuke Konishi
2023-02-15 1:52 ` [syzbot] [nilfs2?] INFO: task hung in nilfs_segctor_thread Hillf Danton
2023-02-15 6:02 ` Yu Zhao
2023-02-15 8:52 ` Dmitry Vyukov [this message]
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=CACT4Y+bKBHus8oe5cMtSfdtG9mMGZGUywA1k_UYCSrwfXWv44A@mail.gmail.com \
--to=dvyukov@google.com \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yuzhao@google.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.