The man page states that simply specifying the -g option will use the
default Android options. However, mkfs.f2fs currently requires the user
to specify `-g android`. This makes the behavior of mkfs.f2fs match the
man page.
Signed-off-by: John A. Leuenhagen
---
mkfs/f2fs_format_main.c | 5 ++---
The pull request you sent on Sun, 13 Dec 2020 21:53:27 -0800:
> https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fsverity-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/51895d58c7c0c65afac21570cc14a7189942959a
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 13 Dec 2020 21:50:19 -0800:
> https://git.kernel.org/pub/scm/fs/fscrypt/fscrypt.git tags/fscrypt-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7c7fdaf6ad9fe868553c2e1fc8a920249820ac3e
Thank you!
--
Deet-doot-dot, I am a b
f2fs does not natively support extents in metadata, 'extent' in f2fs
is used as a virtual concept, so in f2fs_fiemap() interface, it needs
to tag FIEMAP_EXTENT_MERGED flag to indicated the extent status is a
result of merging.
Signed-off-by: Chao Yu
---
fs/f2fs/data.c | 1 +
1 file changed, 1 in
