f2fs: unset atomic/volatile flag in f2fs_release_file
authorJaegeuk Kim <jaegeuk@kernel.org>
Mon, 11 Apr 2016 20:15:10 +0000 (13:15 -0700)
committerJaegeuk Kim <jaegeuk@kernel.org>
Fri, 15 Apr 2016 15:49:47 +0000 (08:49 -0700)
commit26dc3d4424e9f4764d633bd8f9309a01e6f364dd
treebab1db803fd140418d9ed499b7ff63a6d34f746e
parentde5307e46d28aa26ffd6f2048398b6303e134a67
f2fs: unset atomic/volatile flag in f2fs_release_file

The atomic/volatile operation should be done in pair of start and commit
ioctl.
For example, if a killed process remains open-ended atomic operation, we should
drop its flag as well as its atomic data. Otherwise, if sqlite initiates another
operation which doesn't require atomic writes, it will lose every data, since
f2fs still treats with them as atomic writes; nobody will trigger its commit.

Reported-by: Miao Xie <miaoxie@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/file.c
fs/f2fs/segment.c
This page took 0.024715 seconds and 5 git commands to generate.