Re: [syzbot] [nilfs2?] INFO: task hung in nilfs_segctor_thread

Re: [syzbot] [nilfs2?] INFO: task hung in nilfs_segctor_thread

[Hillf Danton]

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
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+f0c4082ce5ebebdac63b@syzkaller.appspotmail.com
> 
> INFO: task segctord:5067 blocked for more than 143 seconds.
>       Not tainted 6.2.0-rc8-syzkaller-00015-gf6feea56f66d #0
> "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
> task:segctord        state:D stack:23456 pid:5067  ppid:2      flags:0x00004000
> Call Trace:
>  <TASK>
>  context_switch kernel/sched/core.c:5293 [inline]
>  __schedule+0x1409/0x43f0 kernel/sched/core.c:6606
>  schedule+0xc3/0x190 kernel/sched/core.c:6682
>  rwsem_down_write_slowpath+0xfcf/0x14a0 kernel/locking/rwsem.c:1190
>  nilfs_transaction_lock+0x25c/0x4f0 fs/nilfs2/segment.c:357
>  nilfs_segctor_thread_construct fs/nilfs2/segment.c:2486 [inline]
>  nilfs_segctor_thread+0x52f/0x1140 fs/nilfs2/segment.c:2570
>  kthread+0x270/0x300 kernel/kthread.c:376
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
>  </TASK>
> 
> Showing all locks held in the system:
> 1 lock held by rcu_tasks_kthre/12:
>  #0: ffffffff8cf258d0 (rcu_tasks.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xce0 kernel/rcu/tasks.h:507
> 1 lock held by rcu_tasks_trace/13:
>  #0: ffffffff8cf260d0 (rcu_tasks_trace.tasks_gp_mutex){+.+.}-{3:3}, at: rcu_tasks_one_gp+0x26/0xce0 kernel/rcu/tasks.h:507
> 1 lock held by khungtaskd/28:
>  #0: ffffffff8cf25700 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
> 2 locks held by getty/4745:
>  #0: ffff88802c2eb098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x25/0x70 drivers/tty/tty_ldisc.c:244
>  #1: ffffc900015b02f0 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x6ab/0x1db0 drivers/tty/n_tty.c:2177
> 3 locks held by syz-executor996/5065:
> 1 lock held by segctord/5067:
>  #0: ffff888017ce92a0 (&nilfs->ns_segctor_sem){++++}-{3:3}, at: nilfs_transaction_lock+0x25c/0x4f0 fs/nilfs2/segment.c:357
> 
> =============================================
> 
> NMI backtrace for cpu 1
> CPU: 1 PID: 28 Comm: khungtaskd Not tainted 6.2.0-rc8-syzkaller-00015-gf6feea56f66d #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
> Call Trace:
>  <TASK>
>  __dump_stack lib/dump_stack.c:88 [inline]
>  dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106
>  nmi_cpu_backtrace+0x4e5/0x560 lib/nmi_backtrace.c:111
>  nmi_trigger_cpumask_backtrace+0x1b4/0x3f0 lib/nmi_backtrace.c:62
>  trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
>  check_hung_uninterruptible_tasks kernel/hung_task.c:220 [inline]
>  watchdog+0xf70/0xfb0 kernel/hung_task.c:377
>  kthread+0x270/0x300 kernel/kthread.c:376
>  ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:308
>  </TASK>
> Sending NMI from CPU 1 to CPUs 0:
> NMI backtrace for cpu 0
> CPU: 0 PID: 5065 Comm: syz-executor996 Not tainted 6.2.0-rc8-syzkaller-00015-gf6feea56f66d #0
> Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/21/2023
> RIP: 0010:__lock_release kernel/locking/lockdep.c:5372 [inline]
> RIP: 0010:lock_release+0x333/0xaa0 kernel/locking/lockdep.c:5688
> Code: 00 f0 ff 42 0f b6 04 3b 84 c0 0f 85 7e 05 00 00 45 89 2e 41 81 fd ff ff 0f 00 0f 87 ff 02 00 00 48 8b 44 24 40 42 0f b6 04 38 <84> c0 0f 85 34 05 00 00 89 16 4c 89 e0 48 c1 e8 03 42 80 3c 38 00
> RSP: 0018:ffffc90003def1c0 EFLAGS: 00000087
> RAX: 0000000000000000 RBX: 1ffff11004d808aa RCX: ffffc90003def203
> RDX: 0000000000000003 RSI: ffff888026c044b0 RDI: ffff888026c04530
> RBP: ffffc90003def2f0 R08: dffffc0000000000 R09: fffffbfff1ca4ece
> R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888026c04530
> R13: 0000000000020021 R14: ffff888026c04550 R15: dffffc0000000000
> FS:  0000555556f2e300(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000056435c9b6680 CR3: 000000001e10a000 CR4: 00000000003506f0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
>  <TASK>
>  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
Hillf

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/mm/swap.c?id=f6feea56f66d#n490

>  __nilfs_get_page_block fs/nilfs2/page.c:42 [inline]
>  nilfs_grab_buffer+0x3d3/0x540 fs/nilfs2/page.c:61
>  nilfs_mdt_submit_block+0xd7/0x8f0 fs/nilfs2/mdt.c:121
>  nilfs_mdt_read_block+0xeb/0x430 fs/nilfs2/mdt.c:176
>  nilfs_mdt_get_block+0x12d/0xbb0 fs/nilfs2/mdt.c:251
>  nilfs_sufile_get_segment_usage_block fs/nilfs2/sufile.c:92 [inline]
>  nilfs_sufile_truncate_range fs/nilfs2/sufile.c:679 [inline]
>  nilfs_sufile_resize+0x7a3/0x12b0 fs/nilfs2/sufile.c:777
>  nilfs_resize_fs+0x20c/0xed0 fs/nilfs2/super.c:422
>  nilfs_ioctl_resize fs/nilfs2/ioctl.c:1033 [inline]
>  nilfs_ioctl+0x137c/0x2440 fs/nilfs2/ioctl.c:1301
>  vfs_ioctl fs/ioctl.c:51 [inline]
>  __do_sys_ioctl fs/ioctl.c:870 [inline]
>  __se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
>  do_syscall_x64 arch/x86/entry/common.c:50 [inline]
>  do_syscall_64+0x41/0xc0 arch/x86/entry/common.c:80
>  entry_SYSCALL_64_after_hwframe+0x63/0xcd
> RIP: 0033:0x7fada4f355f9
> Code: Unable to access opcode bytes at 0x7fada4f355cf.
> RSP: 002b:00007ffdc80a3908 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
> RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fada4f355f9
> RDX: 0000000020000040 RSI: 0000000040086e8b RDI: 0000000000000006
> RBP: 0000000000000000 R08: 00007fada4fa3ec0 R09: 00007fada4fa3ec0
> R10: 00007fada4fa3ec0 R11: 0000000000000246 R12: 00007ffdc80a3930
> R13: 0000000000000000 R14: 431bde82d7b634db R15: 0000000000000000
>  </TASK>
> INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to run: 1.549 msecs

Re: [syzbot] [nilfs2?] INFO: task hung in nilfs_segctor_thread

[Yu Zhao]

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.)

Re: [syzbot] [nilfs2?] INFO: task hung in nilfs_segctor_thread

[Dmitry Vyukov]

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

Re: [syzbot] [nilfs2?] INFO: task hung in nilfs_segctor_thread

[naseriamin080]

Sent from my iPhone