diff options
| author | Jaegeuk Kim <jaegeuk@kernel.org> | 2018-07-27 12:15:11 +0300 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2018-08-01 21:52:36 +0300 |
| commit | 455e3a5887ee7ebec5c885a8f398c2c3c0a33165 (patch) | |
| tree | 83f2e4f0dadb9be1197a6421b7fadd818e07fe61 /fs/f2fs/data.c | |
| parent | 797c1cb56ba58bf42742e9446226345a6216d832 (diff) | |
| download | linux-455e3a5887ee7ebec5c885a8f398c2c3c0a33165.tar.xz | |
f2fs: don't allow any writes on aborted atomic writes
In order to prevent abusing atomic writes by abnormal users, we've added a
threshold, 20% over memory footprint, which disallows further atomic writes.
Previously, however, SQLite doesn't know the files became normal, so that
it could write stale data and commit on revoked normal database file.
Once f2fs detects such the abnormal behavior, this patch tries to avoid further
writes in write_begin().
Reviewed-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/data.c')
| -rw-r--r-- | fs/f2fs/data.c | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/fs/f2fs/data.c b/fs/f2fs/data.c index 7f860405cd6e..5d152de30449 100644 --- a/fs/f2fs/data.c +++ b/fs/f2fs/data.c @@ -2291,8 +2291,9 @@ static int f2fs_write_begin(struct file *file, struct address_space *mapping, trace_f2fs_write_begin(inode, pos, len, flags); - if (f2fs_is_atomic_file(inode) && - !f2fs_available_free_memory(sbi, INMEM_PAGES)) { + if ((f2fs_is_atomic_file(inode) && + !f2fs_available_free_memory(sbi, INMEM_PAGES)) || + is_inode_flag_set(inode, FI_ATOMIC_REVOKE_REQUEST)) { err = -ENOMEM; drop_atomic = true; goto fail; |