diff options
| author |   Jaegeuk Kim <jaegeuk@kernel.org> | 2017-07-24 19:46:29 -0700 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2017-07-28 17:49:01 -0700 |
| commit | 7a10f0177e117e9935ee9e5c595fcf3c57215de5 (patch) | |
| tree | 5b8f062a85ac3d175d0686323fc4c051ce484a17 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | f2fs: give a try to do atomic write in -ENOMEM case (diff) | |
| download | linux-dev-7a10f0177e117e9935ee9e5c595fcf3c57215de5.tar.xz linux-dev-7a10f0177e117e9935ee9e5c595fcf3c57215de5.zip | |
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>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions