| commit | 01d4b3e708adc74f76d6a907f7ee8ce1bfc1895f | [log] [tgz] |
|---|---|---|
| author | Jaegeuk Kim <jaegeuk@kernel.org> | Thu Apr 14 16:48:52 2016 -0700 |
| committer | chrmhoffmann <chrmhoffmann@gmail.com> | Mon Nov 13 22:14:36 2017 +0100 |
| tree | df1cf320a087a206471a91c8a780fb127b7e8ff0 | |
| parent | 73e195d1a3273abc1d4c362b6ba37b02b1c1d818 [diff] |
f2fs: avoid writing 0'th page in volatile writes The first page of volatile writes usually contains a sort of header information which will be used for recovery. (e.g., journal header of sqlite) If this is written without other journal data, user needs to handle the stale journal information. Acked-by: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>