diff options
| author | Sahitya Tummala <stummala@codeaurora.org> | 2019-02-04 11:06:53 +0300 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2019-03-06 06:58:06 +0300 |
| commit | 9083977dabf3833298ddcd40dee28687f1e6b483 (patch) | |
| tree | 8461f2fb89d3ff2e56ba5982fcc95a71f6c710fd /fs/f2fs/super.c | |
| parent | c42d28ce3e16dbd88e575c0acfda96d221dae2c9 (diff) | |
| download | linux-9083977dabf3833298ddcd40dee28687f1e6b483.tar.xz | |
f2fs: do not use mutex lock in atomic context
Fix below warning coming because of using mutex lock in atomic context.
BUG: sleeping function called from invalid context at kernel/locking/mutex.c:98
in_atomic(): 1, irqs_disabled(): 0, pid: 585, name: sh
Preemption disabled at: __radix_tree_preload+0x28/0x130
Call trace:
dump_backtrace+0x0/0x2b4
show_stack+0x20/0x28
dump_stack+0xa8/0xe0
___might_sleep+0x144/0x194
__might_sleep+0x58/0x8c
mutex_lock+0x2c/0x48
f2fs_trace_pid+0x88/0x14c
f2fs_set_node_page_dirty+0xd0/0x184
Do not use f2fs_radix_tree_insert() to avoid doing cond_resched() with
spin_lock() acquired.
Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/super.c')
0 files changed, 0 insertions, 0 deletions