This patch allows users to pin files.
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/file.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
index b164f48e0f31..f8d46df8fa9e 100644
--- a/fs/f2fs/file.c
+++ b/fs/f2fs/file.c
@@ -2964,9 +2964,6 @@ static int f2fs_ioc_se
With the commit <979b25727800> ("fsck.f2fs: check validity of nat journal"),
there is a serious data loss issue observed during sudden power off tests.
The reason is due to incorrect update of journal->n_nats in that patch.
When fsck encounters a nat journal entry with invalid blkaddr/nid, it
upda
https://bugzilla.kernel.org/show_bug.cgi?id=204043
Chao Yu (c...@kernel.org) changed:
What|Removed |Added
Status|NEW |ASSIGNED
CC|
build_sit_info() allocate all bitmaps for each segment one by one,
it's quite low efficiency, this pach changes to allocate large
continuous memory at a time, and divide it and assign for each bitmaps
of segment. For large size image, it can expect improving its mount
speed.
Signed-off-by: Chen Go
On 2019/7/3 23:33, Ocean Chen wrote:
> blk_off might over 512 due to fs corrupt and should
> be checked before being used.
> Use ENTRIES_IN_SUM to protect invalid memory access.
>
> --
> v2:
> - fix typo
> v3:
> - check blk_off before being used
> --
> Signed-off-by: Ocean Chen
> ---
> fs/f2fs/s
Hi Ocean,
On 2019/7/3 23:03, Ocean Chen wrote:
> Hi Yu Chao,
>
> The cur_data_segno only was checked in mount process. In terms of
> security concern, it's better to check value before using it. I know the
Could you explain more about security concern.. Do you get any report from user
or tools t