From: Chao Yu
[ Upstream commit 1773f63d108b1b9b9d053d8c95f8300c556f93b8 ]
F2FS-fs (dm-55): access invalid blkaddr:972878540
Call trace:
dump_backtrace+0xec/0x128
show_stack+0x18/0x28
dump_stack_lvl+0x40/0x88
dump_stack+0x18/0x24
__f2fs_is_valid_blkaddr+0x360/0x3b4
f2fs_is_valid_blkaddr+0x
From: Jaegeuk Kim
[ Upstream commit e23ab8028de0d92df5921a570f5212c0370db3b5 ]
Let's return errors caught by the generic checks. This fixes generic/494 where
it expects to see EBUSY by setattr_prepare instead of EINVAL by f2fs for active
swapfile.
Reviewed-by: Chao Yu
Signed-off-by: Jaegeuk Ki
On 08/08, 王晓珺 wrote:
> 在 2025/8/8 12:16, Chao Yu 写道:
> > Xiaojun,
> >
> > I just notice generic/483 will fail w/ this change, can you please take a
> > look?
> >
> > Thanks,
>
> Hi Chao,
>
> OK, Thanks for pointing out the issue.
Yeah, I'm also hitting several failures in xfstests. Hence, I drop
在 8/8/2025 6:57 AM, Jaegeuk Kim 写道:
> By the way, can we also add some testcases in xfstests to check all this
> works as intended?
Thank you for the suggestion. I'll consider it further and add relevant
testcases in xfstests if possible.
Thanks,
>
> On 08/07, Chunhai Guo wrote:
>> This patch
在 8/8/2025 8:54 AM, Chao Yu 写道:
> Chunhai, can we test selinux case as well? It may need to revert selinux fix
> to find out the problem scenario first.
Yes. I tried reverting the selinux fix, but couldn't reproduce the problem.
Thanks,
>
> Thanks,
>
> On 2025/8/8 06:57, Jaegeuk Kim wrote:
>>
On 8/8/2025 5:48 PM, Liao Yuanhong wrote:
Currently, we have encountered some issues while testing ZUFS. In
situations near the storage limit (e.g., 50GB remaining), and after
simulating fragmentation by repeatedly writing and deleting data, we found
that application installation and startup test
Currently, we have encountered some issues while testing ZUFS. In
situations near the storage limit (e.g., 50GB remaining), and after
simulating fragmentation by repeatedly writing and deleting data, we found
that application installation and startup tests conducted after idling for
a few minutes t
On 8/8/2025 4:51 PM, Chao Yu wrote:
On 8/8/2025 3:29 PM, Liao Yuanhong wrote:
Currently, we have encountered some issues while testing ZUFS. In
situations near the storage limit (e.g., 50GB remaining), and after
simulating fragmentation by repeatedly writing and deleting data, we
found
that ap
On 8/8/2025 3:29 PM, Liao Yuanhong wrote:
Currently, we have encountered some issues while testing ZUFS. In
situations near the storage limit (e.g., 50GB remaining), and after
simulating fragmentation by repeatedly writing and deleting data, we found
that application installation and startup test
w/ below change [1], f2fs will enable lookup_mode=perf by default, it
will change f2fs dirent lookup method from linear based lookup to hash
based lookup.
So that, f2fs will ignore sb.s_encoding_flags by default, which is not
compatible w/ f2fs/012 testcase, in where it will control lookup method
Currently, we have encountered some issues while testing ZUFS. In
situations near the storage limit (e.g., 50GB remaining), and after
simulating fragmentation by repeatedly writing and deleting data, we found
that application installation and startup tests conducted after idling for
a few minutes t
11 matches
Mail list logo
