-start atomic write
-set_page_dirty
-register_inmem_page
<--- truncate or punch hole
-commit atomic write
Here, may cause memory reclaim painc for page->mapping is null,
but private is -1.
Signed-off-by: Yunlei He
---
fs/f2fs/data.c| 8
The crc_offset towards or beyond the end of block is wrong,
sanity check it.
Signed-off-by: Kinglong Mee
---
fsck/mount.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fsck/mount.c b/fsck/mount.c
index fc4cca8..c54bb95 100644
--- a/fsck/mount.c
+++ b/fsck/mount.c
@@ -54
The crc_offset towards or beyond the end of block is wrong,
sanity check it.
Signed-off-by: Kinglong Mee
---
fs/f2fs/checkpoint.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/checkpoint.c b/fs/f2fs/checkpoint.c
index bd75546..f146700 100644
--- a/fs/f2fs/checkpoint
It's migrated from e4crypt.
Adds an example to the f2fscrypt manpages.
v3, add /tools/f2fscrypt to .gitignore
v2, migrate those micro defines for encrypt to f2fs internal,
drop unless of libsha etc.
Signed-off-by: Kinglong Mee
---
.gitignore| 1 +
tools/Makefile.am | 5 +-
tools
Showing directory tree reuses dbg_lv that if setting "-t",
fsck.f2fs does not show any others.
Users may want much information include the debug info and directory tree.
Signed-off-by: Kinglong Mee
---
fsck/fsck.c | 2 +-
fsck/main.c | 4 ++--
include/f2fs_fs.h | 1 +
3 files change
On Tue, Feb 21, 2017 at 03:07:11PM -0800, Eric Biggers wrote:
> From: Eric Biggers
>
> Filesystem encryption ostensibly supported revoking a keyring key that
> had been used to "unlock" encrypted files, causing those files to become
> "locked" again. This was, however, buggy for several reasons,
On 03/15, Yunlei He wrote:
> -start atomic write
>-set_page_dirty
> -register_inmem_page
> <--- truncate or punch hole
SQLite bug?
> -commit atomic write
>
> Here, may cause memory reclaim painc for page->mapping is null,
> but private is -1.
>
>
