Searched hist:"509 f1010e4fc55e2dbfc036317afd573ccd0931c" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | segment.c | diff 509f1010e4fc55e2dbfc036317afd573ccd0931c Tue Apr 20 20:54:55 CDT 2021 Chao Yu <yuchao0@huawei.com> f2fs: avoid using native allocate_segment_by_default()
As we did for other cases, in fix_curseg_write_pointer(), let's
use wrapped f2fs_allocate_new_section() instead of native
allocate_segment_by_default(), by this way, it fixes to cover
segment allocation with curseg_lock and sentry_lock.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | file.c | diff 509f1010e4fc55e2dbfc036317afd573ccd0931c Tue Apr 20 20:54:55 CDT 2021 Chao Yu <yuchao0@huawei.com> f2fs: avoid using native allocate_segment_by_default()
As we did for other cases, in fix_curseg_write_pointer(), let's
use wrapped f2fs_allocate_new_section() instead of native
allocate_segment_by_default(), by this way, it fixes to cover
segment allocation with curseg_lock and sentry_lock.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | f2fs.h | diff 509f1010e4fc55e2dbfc036317afd573ccd0931c Tue Apr 20 20:54:55 CDT 2021 Chao Yu <yuchao0@huawei.com> f2fs: avoid using native allocate_segment_by_default()
As we did for other cases, in fix_curseg_write_pointer(), let's
use wrapped f2fs_allocate_new_section() instead of native
allocate_segment_by_default(), by this way, it fixes to cover
segment allocation with curseg_lock and sentry_lock.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|