[f2fs-dev] [PATCH] f2fs: fix data corruption issue with hardware encryption

Direct IO can be used in case of hardware encryption. The following scenario results into data corruption issue in this path - Thread A - Thread B- -> write file#1 in direct IO -> GC gets kicked in ->

[f2fs-dev] [PATCH] fsck.f2fs: do not hard-code encrypted filename length to avoid heap buffer overflow

From: Randall Huang If the len is less than 24, heap buffer overflow is reported. Signed-off-by: Randall Huang Signed-off-by: Jaegeuk Kim --- fsck/fsck.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/fsck/fsck.c b/fsck/fsck.c index 85d9823..1fc168f 100644 --- a/fsck/f

Re: [f2fs-dev] [PATCH] fsck.f2fs: do not check segment type of empty curseg

Sorry, this seems wrong, please ignore this :( On 2018/10/8 21:09, Sheng Yong wrote: If a curseg is not used, its SIT entry may have an inconsistent type. This will be fixed during recover. Fixes: df8065e52928be ("fsck.f2fs: introduce fsck_chk_curseg_info") Signed-off-by: Sheng Yong --- fsck