diff options
| author | Chao Yu <yuchao0@huawei.com> | 2016-11-17 15:53:11 +0300 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2016-11-25 21:16:01 +0300 |
| commit | 04d47e673863c637a2b44ad34a558aeb5d0a727e (patch) | |
| tree | e35422bfca5033adda54c0716c498c5b75895677 /tools/perf/scripts/python/call-graph-from-sql.py | |
| parent | d40a43af0a57a017eba9ad2679183791587ceb6a (diff) | |
| download | linux-04d47e673863c637a2b44ad34a558aeb5d0a727e.tar.xz | |
f2fs: fix to account total free nid correctly
Thread A Thread B Thread C
- f2fs_create
- f2fs_new_inode
- f2fs_lock_op
- alloc_nid
alloc last nid
- f2fs_unlock_op
- f2fs_create
- f2fs_new_inode
- f2fs_lock_op
- alloc_nid
as node count still not
be increased, we will
loop in alloc_nid
- f2fs_write_node_pages
- f2fs_balance_fs_bg
- f2fs_sync_fs
- write_checkpoint
- block_operations
- f2fs_lock_all
- f2fs_lock_op
While creating new inode, we do not allocate and account nid atomically,
so that when there is almost no free nids left, we may encounter deadloop
like above stack.
In order to avoid that, reuse nm_i::available_nids for accounting free nids
and make nid allocation and counting being atomical during node creation.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-sql.py')
0 files changed, 0 insertions, 0 deletions