Searched hist:"7 a10f0177e117e9935ee9e5c595fcf3c57215de5" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | file.c | diff 7a10f0177e117e9935ee9e5c595fcf3c57215de5 Mon Jul 24 21:46:29 CDT 2017 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: don't give partially written atomic data from process crash
This patch resolves the below scenario.
== Process 1 == == Process 2 ==
open(w) open(rw)
begin
write(new_#1)
process_crash
f_op->flush
locks_remove_posix
f_op>release
read (new_#1)
In order to avoid corrupted database caused by new_#1, we must do roll-back
at process_crash time. In order to check that, this patch keeps task which
triggers transaction begin, and does roll-back in f_op->flush before removing
file locks.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | f2fs.h | diff 7a10f0177e117e9935ee9e5c595fcf3c57215de5 Mon Jul 24 21:46:29 CDT 2017 Jaegeuk Kim <jaegeuk@kernel.org> f2fs: don't give partially written atomic data from process crash
This patch resolves the below scenario.
== Process 1 == == Process 2 ==
open(w) open(rw)
begin
write(new_#1)
process_crash
f_op->flush
locks_remove_posix
f_op>release
read (new_#1)
In order to avoid corrupted database caused by new_#1, we must do roll-back
at process_crash time. In order to check that, this patch keeps task which
triggers transaction begin, and does roll-back in f_op->flush before removing
file locks.
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|