From: Daeho Jeong
In cases of removing memory donation, we need to handle some error cases
like ENOENT and EACCES (indicating the range already has been donated).
Signed-off-by: Daeho Jeong
---
fs/f2fs/f2fs.h | 1 +
fs/f2fs/file.c | 21 ++---
fs/f2fs/shrinker.c | 5 ++
Dear Matthew,
Hope you are doing well.
I've recently made some progress in enabling iomap support for
buffered read and buffered write on regular files in f2fs. However,
I'm encountering significant challenges when it comes to supporting
iomap for page writeback.
Currently, the f2fs_write_cache_p
[ cut here ]
WARNING: CPU: 3 PID: 579 at fs/f2fs/segment.c:2832 new_curseg+0x5e8/0x6dc
pc : new_curseg+0x5e8/0x6dc
Call trace:
new_curseg+0x5e8/0x6dc
f2fs_allocate_data_block+0xa54/0xe28
do_write_page+0x6c/0x194
f2fs_do_write_node_page+0x38/0x78
__write_node_page+0x248/
Let fsck.f2fs recognize STOP_CP_REASON_CORRUPTED_FREE_BITMAP.
Signed-off-by: Chao Yu
---
fsck/mount.c | 1 +
include/f2fs_fs.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/fsck/mount.c b/fsck/mount.c
index 4fd26a6..08b2687 100644
--- a/fsck/mount.c
+++ b/fsck/mount.c
@@ -729,6 +729