A length that exceeds the real size of the inode may be
specified from user, although these out-of-range areas
are not mapped, but they still need to be check in
while loop, which is unnecessary.
Signed-off-by: Zhiguo Niu
---
v3: adjust code positions according to Chao's suggestions
v2: check
As reported by Yi Zhang in mailing list [1], kernel warning was catched
during zbd/010 test as below:
./check zbd/010
zbd/010 (test gap zone support with F2FS)[failed]
runtime... 3.752s
something found in dmesg:
[ 4378.146781] run blktests zbd/010 at
On 2024/3/27 9:26, Zhiguo Niu wrote:
On Tue, Mar 26, 2024 at 7:11 PM Chao Yu wrote:
On 2024/3/25 13:56, Zhiguo Niu wrote:
A length that exceeds the real size of the inode may be
specified from user, although these out-of-range areas
are not mapped, but they still need to be check in
while
On 2024/3/26 14:10, Yunlei He wrote:
In f2fs_remount, SB_INLINECRYPT flag will be clear and re-set.
If create new file or open file during this gap, these files
will not use inlinecrypt. Worse case, it may lead to data
corruption if wrappedkey_v0 is enable.
Thread A:
