Hi Dave,
Thank you for the report.
I've figured out that there is a bug in f2fs_insert_range, which dropps a dirty
data page when flushing blocks after finsert is done.
That is caused by not updating i_size instantly.
I wrote a patch for this like below.
Thanks,
>From 108daea1bd02014d118aa1dbc
This patch adopts:
ext4 crypto: add missing locking for keyring_key access
Signed-off-by: Theodore Ts'o
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/crypto_key.c | 4
1 file changed, 4 insertions(+)
diff --git a/fs/f2fs/crypto_key.c b/fs/f2fs/crypto_key.c
index 2d491ee..9094fca 100644
-
This patch adopts:
ext4 crypto: fix spelling typo in comment
Signed-off-by: Laurent Navet
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/crypto_key.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/f2fs/crypto_key.c b/fs/f2fs/crypto_key.c
index fc0e3cc..2d491ee 100644
---
This patch adopts:
ext4 crypto: ext4_page_crypto() doesn't need a encryption context
Since ext4_page_crypto() doesn't need an encryption context (at least
not any more), this allows us to simplify a number function signature
and also allows us to avoid needing to allocate a context in
ext4
This patch adopts:
ext4 crypto: check for too-short encrypted file names
An encrypted file name should never be shorter than an 16 bytes, the
AES block size. The 3.10 crypto layer will oops and crash the kernel
if ciphertext shorter than the block size is passed to it.
Fortunately, in mo
This patch adopts:
ext4 crypto: replace some BUG_ON()'s with error checks
Signed-off-by: Theodore Ts'o
Signed-off-by: Jaegeuk Kim
---
fs/f2fs/crypto.c | 1 -
fs/f2fs/crypto_fname.c | 2 --
fs/f2fs/crypto_key.c | 15 ---
3 files changed, 12 insertions(+), 6 deletion
