From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: use spin_lock to avoid hang
Date: Wed, 9 Mar 2022 18:51:32 -0800 [thread overview]
Message-ID: <YilntIMrQchFfq9n@google.com> (raw)
In-Reply-To: <7b12573b-cad4-45b0-9e8a-9cc40a08b856@kernel.org>
On 03/10, Chao Yu wrote:
> On 2022/3/10 5:48, Jaegeuk Kim wrote:
> > [14696.634553] task:cat state:D stack: 0 pid:1613738 ppid:1613735 flags:0x00000004
> > [14696.638285] Call Trace:
> > [14696.639038] <TASK>
> > [14696.640032] __schedule+0x302/0x930
> > [14696.640969] schedule+0x58/0xd0
> > [14696.641799] schedule_preempt_disabled+0x18/0x30
> > [14696.642890] __mutex_lock.constprop.0+0x2fb/0x4f0
> > [14696.644035] ? mod_objcg_state+0x10c/0x310
> > [14696.645040] ? obj_cgroup_charge+0xe1/0x170
> > [14696.646067] __mutex_lock_slowpath+0x13/0x20
> > [14696.647126] mutex_lock+0x34/0x40
> > [14696.648070] stat_show+0x25/0x17c0 [f2fs]
> > [14696.649218] seq_read_iter+0x120/0x4b0
> > [14696.650289] ? aa_file_perm+0x12a/0x500
> > [14696.651357] ? lru_cache_add+0x1c/0x20
> > [14696.652470] seq_read+0xfd/0x140
> > [14696.653445] full_proxy_read+0x5c/0x80
> > [14696.654535] vfs_read+0xa0/0x1a0
> > [14696.655497] ksys_read+0x67/0xe0
> > [14696.656502] __x64_sys_read+0x1a/0x20
> > [14696.657580] do_syscall_64+0x3b/0xc0
> > [14696.658671] entry_SYSCALL_64_after_hwframe+0x44/0xae
> > [14696.660068] RIP: 0033:0x7efe39df1cb2
> > [14696.661133] RSP: 002b:00007ffc8badd948 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> > [14696.662958] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007efe39df1cb2
> > [14696.664757] RDX: 0000000000020000 RSI: 00007efe399df000 RDI: 0000000000000003
> > [14696.666542] RBP: 00007efe399df000 R08: 00007efe399de010 R09: 00007efe399de010
> > [14696.668363] R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000000000
> > [14696.670155] R13: 0000000000000003 R14: 0000000000020000 R15: 0000000000020000
> > [14696.671965] </TASK>
> > [14696.672826] task:umount state:D stack: 0 pid:1614985 ppid:1614984 flags:0x00004000
> > [14696.674930] Call Trace:
> > [14696.675903] <TASK>
> > [14696.676780] __schedule+0x302/0x930
> > [14696.677927] schedule+0x58/0xd0
> > [14696.679019] schedule_preempt_disabled+0x18/0x30
> > [14696.680412] __mutex_lock.constprop.0+0x2fb/0x4f0
> > [14696.681783] ? destroy_inode+0x65/0x80
> > [14696.683006] __mutex_lock_slowpath+0x13/0x20
> > [14696.684305] mutex_lock+0x34/0x40
> > [14696.685442] f2fs_destroy_stats+0x1e/0x60 [f2fs]
> > [14696.686803] f2fs_put_super+0x158/0x390 [f2fs]
> > [14696.688238] generic_shutdown_super+0x7a/0x120
> > [14696.689621] kill_block_super+0x27/0x50
> > [14696.690894] kill_f2fs_super+0x7f/0x100 [f2fs]
> > [14696.692311] deactivate_locked_super+0x35/0xa0
> > [14696.693698] deactivate_super+0x40/0x50
> > [14696.694985] cleanup_mnt+0x139/0x190
> > [14696.696209] __cleanup_mnt+0x12/0x20
> > [14696.697390] task_work_run+0x64/0xa0
> > [14696.698587] exit_to_user_mode_prepare+0x1b7/0x1c0
> > [14696.700053] syscall_exit_to_user_mode+0x27/0x50
> > [14696.701418] do_syscall_64+0x48/0xc0
> > [14696.702630] entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> Any race case here? I didn't catch the root cause here...
This is the only clue that I could use. :(
> Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: use spin_lock to avoid hang
Date: Wed, 9 Mar 2022 18:51:32 -0800 [thread overview]
Message-ID: <YilntIMrQchFfq9n@google.com> (raw)
In-Reply-To: <7b12573b-cad4-45b0-9e8a-9cc40a08b856@kernel.org>
On 03/10, Chao Yu wrote:
> On 2022/3/10 5:48, Jaegeuk Kim wrote:
> > [14696.634553] task:cat state:D stack: 0 pid:1613738 ppid:1613735 flags:0x00000004
> > [14696.638285] Call Trace:
> > [14696.639038] <TASK>
> > [14696.640032] __schedule+0x302/0x930
> > [14696.640969] schedule+0x58/0xd0
> > [14696.641799] schedule_preempt_disabled+0x18/0x30
> > [14696.642890] __mutex_lock.constprop.0+0x2fb/0x4f0
> > [14696.644035] ? mod_objcg_state+0x10c/0x310
> > [14696.645040] ? obj_cgroup_charge+0xe1/0x170
> > [14696.646067] __mutex_lock_slowpath+0x13/0x20
> > [14696.647126] mutex_lock+0x34/0x40
> > [14696.648070] stat_show+0x25/0x17c0 [f2fs]
> > [14696.649218] seq_read_iter+0x120/0x4b0
> > [14696.650289] ? aa_file_perm+0x12a/0x500
> > [14696.651357] ? lru_cache_add+0x1c/0x20
> > [14696.652470] seq_read+0xfd/0x140
> > [14696.653445] full_proxy_read+0x5c/0x80
> > [14696.654535] vfs_read+0xa0/0x1a0
> > [14696.655497] ksys_read+0x67/0xe0
> > [14696.656502] __x64_sys_read+0x1a/0x20
> > [14696.657580] do_syscall_64+0x3b/0xc0
> > [14696.658671] entry_SYSCALL_64_after_hwframe+0x44/0xae
> > [14696.660068] RIP: 0033:0x7efe39df1cb2
> > [14696.661133] RSP: 002b:00007ffc8badd948 EFLAGS: 00000246 ORIG_RAX: 0000000000000000
> > [14696.662958] RAX: ffffffffffffffda RBX: 0000000000020000 RCX: 00007efe39df1cb2
> > [14696.664757] RDX: 0000000000020000 RSI: 00007efe399df000 RDI: 0000000000000003
> > [14696.666542] RBP: 00007efe399df000 R08: 00007efe399de010 R09: 00007efe399de010
> > [14696.668363] R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000000000
> > [14696.670155] R13: 0000000000000003 R14: 0000000000020000 R15: 0000000000020000
> > [14696.671965] </TASK>
> > [14696.672826] task:umount state:D stack: 0 pid:1614985 ppid:1614984 flags:0x00004000
> > [14696.674930] Call Trace:
> > [14696.675903] <TASK>
> > [14696.676780] __schedule+0x302/0x930
> > [14696.677927] schedule+0x58/0xd0
> > [14696.679019] schedule_preempt_disabled+0x18/0x30
> > [14696.680412] __mutex_lock.constprop.0+0x2fb/0x4f0
> > [14696.681783] ? destroy_inode+0x65/0x80
> > [14696.683006] __mutex_lock_slowpath+0x13/0x20
> > [14696.684305] mutex_lock+0x34/0x40
> > [14696.685442] f2fs_destroy_stats+0x1e/0x60 [f2fs]
> > [14696.686803] f2fs_put_super+0x158/0x390 [f2fs]
> > [14696.688238] generic_shutdown_super+0x7a/0x120
> > [14696.689621] kill_block_super+0x27/0x50
> > [14696.690894] kill_f2fs_super+0x7f/0x100 [f2fs]
> > [14696.692311] deactivate_locked_super+0x35/0xa0
> > [14696.693698] deactivate_super+0x40/0x50
> > [14696.694985] cleanup_mnt+0x139/0x190
> > [14696.696209] __cleanup_mnt+0x12/0x20
> > [14696.697390] task_work_run+0x64/0xa0
> > [14696.698587] exit_to_user_mode_prepare+0x1b7/0x1c0
> > [14696.700053] syscall_exit_to_user_mode+0x27/0x50
> > [14696.701418] do_syscall_64+0x48/0xc0
> > [14696.702630] entry_SYSCALL_64_after_hwframe+0x44/0xae
>
> Any race case here? I didn't catch the root cause here...
This is the only clue that I could use. :(
> Thanks,
next prev parent reply other threads:[~2022-03-10 2:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 21:48 [f2fs-dev] [PATCH 1/2] f2fs: evict inode cache for frozen fs Jaegeuk Kim
2022-03-09 21:48 ` Jaegeuk Kim
2022-03-09 21:48 ` [f2fs-dev] [PATCH 2/2] f2fs: use spin_lock to avoid hang Jaegeuk Kim
2022-03-09 21:48 ` Jaegeuk Kim
2022-03-10 2:23 ` [f2fs-dev] " Chao Yu
2022-03-10 2:23 ` Chao Yu
2022-03-10 2:51 ` Jaegeuk Kim [this message]
2022-03-10 2:51 ` Jaegeuk Kim
2022-03-16 2:33 ` Chao Yu
2022-03-16 2:33 ` Chao Yu
2022-03-10 1:53 ` [f2fs-dev] [PATCH 1/2] f2fs: evict inode cache for frozen fs Chao Yu
2022-03-10 1:53 ` Chao Yu
2022-03-11 3:10 ` Chao Yu
2022-03-11 3:10 ` Chao Yu
2022-03-11 5:22 ` Jaegeuk Kim
2022-03-11 5:22 ` Jaegeuk Kim
2022-03-10 2:52 ` [f2fs-dev] [PATCH 1/2 v2] f2fs: do not expose unwritten blocks to user by DIO Jaegeuk Kim
2022-03-10 2:52 ` Jaegeuk Kim
2022-03-11 5:22 ` [f2fs-dev] [PATCH 1/2 v2] f2fs: don't get FREEZE lock in f2fs_evict_inode in frozen fs Jaegeuk Kim
2022-03-11 5:22 ` Jaegeuk Kim
2022-03-11 7:25 ` [f2fs-dev] " Chao Yu
2022-03-11 7:25 ` Chao Yu
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=YilntIMrQchFfq9n@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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 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.