* [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
@ 2020-10-29 16:40 kitestramuort
2020-10-30 1:50 ` Chao Yu
0 siblings, 1 reply; 10+ messages in thread
From: kitestramuort @ 2020-10-29 16:40 UTC (permalink / raw)
To: linux-f2fs-devel
Hello,
the new rc is generating the error below multiple times a few minutes
after boot.
This is a 970 evo nvme drive formatted with f2fs and mounted with the
following params:
/dev/nvme0n1p4 /home f2fs
rw,noatime,background_gc=on,fsync_mode=nobarrier,inline_xattr,inline_da
ta,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6
0 0
5.9 works fine
F2FS-fs (nvme0n1p4): access invalid blkaddr:2692804519
[ 1405.532414] ------------[ cut here ]------------
[ 1405.532418] WARNING: CPU: 4 PID: 2650 at 0xffffffffa538abb7
[ 1405.532420] Modules linked in: uvcvideo videobuf2_v4l2
videobuf2_vmalloc videobuf2_memops videobuf2_common videodev mc
[ 1405.532442] CPU: 4 PID: 2650 Comm: Cache2 I/O Tainted: G S U
5.10.0-rc1-S #8
[ 1405.532445] Hardware name: 51NB X213s/X213s, BIOS 4.12-3637-
g6ad856825a-dirty 10/28/2020
[ 1405.532448] RIP: 0010:0xffffffffa538abb7
[ 1405.532453] Code: 01 c8 39 c6 73 09 41 8b 42 5c e9 29 fe ff ff 89 f2
48 c7 c6 4d 86 2e a6 48 89 3c 24 e8 38 55 75 00 48 8b 3c 24 f0 80 4f 48
04 <0f> 0b 31 c0 e9 af fe ff ff 41 57 41 56 41 55 41 54 41 89 cc 31 c9
[ 1405.532457] RSP: 0018:ffff9c36c33bf8e0 EFLAGS: 00010206
[ 1405.532461] RAX: 0000000000000036 RBX: 0000000000000369 RCX:
0000000000000000
[ 1405.532464] RDX: ffff8ef0ef51c688 RSI: ffff8ef0ef5177c0 RDI:
ffff8eed80fbe000
[ 1405.532467] RBP: ffff8eedabeaf600 R08: ffffffffa66016a8 R09:
00000000ffffffea
[ 1405.532470] R10: 00000000ffffbfff R11: 80000000ffffc000 R12:
0000000000000001
[ 1405.532472] R13: ffff8eeecbac8000 R14: 0000000000000003 R15:
0000000000001000
[ 1405.532476] FS: 00007f41b1e75640(0000) GS:ffff8ef0ef500000(0000)
knlGS:0000000000000000
[ 1405.532479] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 1405.532482] CR2: 00007f41b0d28425 CR3: 00000001eb446004 CR4:
00000000001706e0
[ 1405.532485] Call Trace:
[ 1405.532489] ? 0xffffffffa53731fb
[ 1405.532492] ? 0xffffffffa536872f
[ 1405.532494] ? 0xffffffffa5368e54
[ 1405.532497] ? 0xffffffffa53698e2
[ 1405.532499] ? 0xffffffffa51151af
[ 1405.532504] ? 0xffffffffa5369d56
[ 1405.532506] ? 0xffffffffa5361470
[ 1405.532509] ? 0xffffffffa5369ea6
[ 1405.532510] ? 0xffffffffa5361492
[ 1405.532512] ? 0xffffffffa5278da6
[ 1405.532515] ? 0xffffffffa52950be
[ 1405.532518] ? 0xffffffffa528f370
[ 1405.532520] ? 0xffffffffa5297830
[ 1405.532523] ? 0xffffffffa528f370
[ 1405.532525] ? 0xffffffffa528f370
[ 1405.532528] ? 0xffffffffa527bfbb
[ 1405.532530] ? 0xffffffffa5b1926d
[ 1405.532531] ? 0xffffffffa5c0007c
[ 1405.532539] CPU: 4 PID: 2650 Comm: Cache2 I/O Tainted: G S U
5.10.0-rc1-S #8
[ 1405.532541] Hardware name: 51NB X213s/X213s, BIOS 4.12-3637-
g6ad856825a-dirty 10/28/2020
[ 1405.532542] Call Trace:
[ 1405.532545] ? 0xffffffffa5ae2a0a
[ 1405.532547] ? 0xffffffffa5ad3e00
[ 1405.532548] ? 0xffffffffa538abb7
[ 1405.532550] ? 0xffffffffa54b502d
[ 1405.532552] ? 0xffffffffa5b1944c
[ 1405.532555] ? 0xffffffffa5b196d8
[ 1405.532557] ? 0xffffffffa5c00a0f
[ 1405.532560] ? 0xffffffffa538abb7
[ 1405.532562] ? 0xffffffffa53731fb
[ 1405.532565] ? 0xffffffffa536872f
[ 1405.532567] ? 0xffffffffa5368e54
[ 1405.532569] ? 0xffffffffa53698e2
[ 1405.532572] ? 0xffffffffa51151af
[ 1405.532576] ? 0xffffffffa5369d56
[ 1405.532578] ? 0xffffffffa5361470
[ 1405.532580] ? 0xffffffffa5369ea6
[ 1405.532582] ? 0xffffffffa5361492
[ 1405.532584] ? 0xffffffffa5278da6
[ 1405.532586] ? 0xffffffffa52950be
[ 1405.532589] ? 0xffffffffa528f370
[ 1405.532591] ? 0xffffffffa5297830
[ 1405.532593] ? 0xffffffffa528f370
[ 1405.532596] ? 0xffffffffa528f370
[ 1405.532598] ? 0xffffffffa527bfbb
[ 1405.532600] ? 0xffffffffa5b1926d
[ 1405.532602] ? 0xffffffffa5c0007c
[ 1405.532605] ---[ end trace 16864b8277e92bfe ]---
regards
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-10-29 16:40 [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr kitestramuort
@ 2020-10-30 1:50 ` Chao Yu
2020-10-30 8:56 ` kitestramuort
0 siblings, 1 reply; 10+ messages in thread
From: Chao Yu @ 2020-10-30 1:50 UTC (permalink / raw)
To: kitestramuort, linux-f2fs-devel
On 2020/10/30 0:40, kitestramuort wrote:
> Hello,
> the new rc is generating the error below multiple times a few minutes
> after boot.
>
> This is a 970 evo nvme drive formatted with f2fs and mounted with the
> following params:
>
> /dev/nvme0n1p4 /home f2fs
> rw,noatime,background_gc=on,fsync_mode=nobarrier,inline_xattr,inline_da
> ta,inline_dentry,flush_merge,extent_cache,mode=adaptive,active_logs=6
> 0 0
>
> 5.9 works fine
>
> F2FS-fs (nvme0n1p4): access invalid blkaddr:2692804519
The blkaddr should have exceeded device's space boundary.
It looks it doesn't print function name in call stack, I can't track into
detail function any further, I checked patches merged in 5.10rc1, however
I got nothing.
Could you please try fsck --dry-run, and share the output?
Thanks,
> [ 1405.532414] ------------[ cut here ]------------
> [ 1405.532418] WARNING: CPU: 4 PID: 2650 at 0xffffffffa538abb7
> [ 1405.532420] Modules linked in: uvcvideo videobuf2_v4l2
> videobuf2_vmalloc videobuf2_memops videobuf2_common videodev mc
> [ 1405.532442] CPU: 4 PID: 2650 Comm: Cache2 I/O Tainted: G S U
> 5.10.0-rc1-S #8
> [ 1405.532445] Hardware name: 51NB X213s/X213s, BIOS 4.12-3637-
> g6ad856825a-dirty 10/28/2020
> [ 1405.532448] RIP: 0010:0xffffffffa538abb7
> [ 1405.532453] Code: 01 c8 39 c6 73 09 41 8b 42 5c e9 29 fe ff ff 89 f2
> 48 c7 c6 4d 86 2e a6 48 89 3c 24 e8 38 55 75 00 48 8b 3c 24 f0 80 4f 48
> 04 <0f> 0b 31 c0 e9 af fe ff ff 41 57 41 56 41 55 41 54 41 89 cc 31 c9
> [ 1405.532457] RSP: 0018:ffff9c36c33bf8e0 EFLAGS: 00010206
> [ 1405.532461] RAX: 0000000000000036 RBX: 0000000000000369 RCX:
> 0000000000000000
> [ 1405.532464] RDX: ffff8ef0ef51c688 RSI: ffff8ef0ef5177c0 RDI:
> ffff8eed80fbe000
> [ 1405.532467] RBP: ffff8eedabeaf600 R08: ffffffffa66016a8 R09:
> 00000000ffffffea
> [ 1405.532470] R10: 00000000ffffbfff R11: 80000000ffffc000 R12:
> 0000000000000001
> [ 1405.532472] R13: ffff8eeecbac8000 R14: 0000000000000003 R15:
> 0000000000001000
> [ 1405.532476] FS: 00007f41b1e75640(0000) GS:ffff8ef0ef500000(0000)
> knlGS:0000000000000000
> [ 1405.532479] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 1405.532482] CR2: 00007f41b0d28425 CR3: 00000001eb446004 CR4:
> 00000000001706e0
> [ 1405.532485] Call Trace:
> [ 1405.532489] ? 0xffffffffa53731fb
> [ 1405.532492] ? 0xffffffffa536872f
> [ 1405.532494] ? 0xffffffffa5368e54
> [ 1405.532497] ? 0xffffffffa53698e2
> [ 1405.532499] ? 0xffffffffa51151af
> [ 1405.532504] ? 0xffffffffa5369d56
> [ 1405.532506] ? 0xffffffffa5361470
> [ 1405.532509] ? 0xffffffffa5369ea6
> [ 1405.532510] ? 0xffffffffa5361492
> [ 1405.532512] ? 0xffffffffa5278da6
> [ 1405.532515] ? 0xffffffffa52950be
> [ 1405.532518] ? 0xffffffffa528f370
> [ 1405.532520] ? 0xffffffffa5297830
> [ 1405.532523] ? 0xffffffffa528f370
> [ 1405.532525] ? 0xffffffffa528f370
> [ 1405.532528] ? 0xffffffffa527bfbb
> [ 1405.532530] ? 0xffffffffa5b1926d
> [ 1405.532531] ? 0xffffffffa5c0007c
> [ 1405.532539] CPU: 4 PID: 2650 Comm: Cache2 I/O Tainted: G S U
> 5.10.0-rc1-S #8
> [ 1405.532541] Hardware name: 51NB X213s/X213s, BIOS 4.12-3637-
> g6ad856825a-dirty 10/28/2020
> [ 1405.532542] Call Trace:
> [ 1405.532545] ? 0xffffffffa5ae2a0a
> [ 1405.532547] ? 0xffffffffa5ad3e00
> [ 1405.532548] ? 0xffffffffa538abb7
> [ 1405.532550] ? 0xffffffffa54b502d
> [ 1405.532552] ? 0xffffffffa5b1944c
> [ 1405.532555] ? 0xffffffffa5b196d8
> [ 1405.532557] ? 0xffffffffa5c00a0f
> [ 1405.532560] ? 0xffffffffa538abb7
> [ 1405.532562] ? 0xffffffffa53731fb
> [ 1405.532565] ? 0xffffffffa536872f
> [ 1405.532567] ? 0xffffffffa5368e54
> [ 1405.532569] ? 0xffffffffa53698e2
> [ 1405.532572] ? 0xffffffffa51151af
> [ 1405.532576] ? 0xffffffffa5369d56
> [ 1405.532578] ? 0xffffffffa5361470
> [ 1405.532580] ? 0xffffffffa5369ea6
> [ 1405.532582] ? 0xffffffffa5361492
> [ 1405.532584] ? 0xffffffffa5278da6
> [ 1405.532586] ? 0xffffffffa52950be
> [ 1405.532589] ? 0xffffffffa528f370
> [ 1405.532591] ? 0xffffffffa5297830
> [ 1405.532593] ? 0xffffffffa528f370
> [ 1405.532596] ? 0xffffffffa528f370
> [ 1405.532598] ? 0xffffffffa527bfbb
> [ 1405.532600] ? 0xffffffffa5b1926d
> [ 1405.532602] ? 0xffffffffa5c0007c
> [ 1405.532605] ---[ end trace 16864b8277e92bfe ]---
>
>
>
> regards
>
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-10-30 1:50 ` Chao Yu
@ 2020-10-30 8:56 ` kitestramuort
2020-10-30 9:06 ` Chao Yu
0 siblings, 1 reply; 10+ messages in thread
From: kitestramuort @ 2020-10-30 8:56 UTC (permalink / raw)
To: Chao Yu, linux-f2fs-devel
On Fri, 2020-10-30 at 09:50 +0800, Chao Yu wrote:
> On 2020/10/30 0:40, kitestramuort wrote:
> > Hello,
> > the new rc is generating the error below multiple times a few
> > minutes
> > after boot.
> >
>
> Could you please try fsck --dry-run, and share the output?
Info: Dry run
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 1692427663 (826380 MB)
Info: MKFS version
"Linux version 4.20.0-arch1-1-ARCH (builduser@heftig-29859) (gcc
version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC
2018"
Info: FSCK version
from "Linux version 5.2.5-arch1-1-ARCH (builduser@heftig-118908) (gcc
version 9.1.0 (GCC)) #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019"
to "Linux version 5.10.0-rc1-S (root@x210) (gcc (GCC) 10.2.0, GNU
ld (GNU Binutils) 2.35.1) #8 SMP PREEMPT Wed Oct 28 18:58:28 CET 2020"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt =
00000000000000000000000000000000
Info: total FS sectors = 1692427656 (826380 MB)
Info: CKPT version = 2847755
Info: checkpoint state = 55 : crc fsck compacted_summary unmount
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x50c]
[FSCK] valid_block_count matching with CP [Ok..]
[0x9589819]
[FSCK] valid_node_count matching with CP (de lookup) [Ok..] [0x2bec97]
[FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x2bec97]
[FSCK] valid_inode_count matched with CP [Ok..] [0x29f985]
[FSCK] free segment_count matched with CP [Ok..] [0x18105]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]
Done: 263.250850 secs
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-10-30 8:56 ` kitestramuort
@ 2020-10-30 9:06 ` Chao Yu
2020-10-30 11:10 ` kitestramuort
0 siblings, 1 reply; 10+ messages in thread
From: Chao Yu @ 2020-10-30 9:06 UTC (permalink / raw)
To: kitestramuort, linux-f2fs-devel
On 2020/10/30 16:56, kitestramuort wrote:
> On Fri, 2020-10-30 at 09:50 +0800, Chao Yu wrote:
>> On 2020/10/30 0:40, kitestramuort wrote:
>>> Hello,
>>> the new rc is generating the error below multiple times a few
>>> minutes
>>> after boot.
>>>
>>
>> Could you please try fsck --dry-run, and share the output?
What's your fsck version? could you try last v1.14 fsck?
https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs-tools.git
> [ 1405.532489] ? 0xffffffffa53731fb
It doesn't print function name in callstack, could you check your linker
option, I guess it needs to add -rdynamic option? not sure.
>
> Info: Dry run
> Info: Segments per section = 1
> Info: Sections per zone = 1
> Info: sector size = 512
> Info: total sectors = 1692427663 (826380 MB)
> Info: MKFS version
> "Linux version 4.20.0-arch1-1-ARCH (builduser@heftig-29859) (gcc
> version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC
> 2018"
> Info: FSCK version
> from "Linux version 5.2.5-arch1-1-ARCH (builduser@heftig-118908) (gcc
> version 9.1.0 (GCC)) #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019"
> to "Linux version 5.10.0-rc1-S (root@x210) (gcc (GCC) 10.2.0, GNU
> ld (GNU Binutils) 2.35.1) #8 SMP PREEMPT Wed Oct 28 18:58:28 CET 2020"
> Info: superblock features = 0 :
> Info: superblock encrypt level = 0, salt =
> 00000000000000000000000000000000
> Info: total FS sectors = 1692427656 (826380 MB)
> Info: CKPT version = 2847755
> Info: checkpoint state = 55 : crc fsck compacted_summary unmount
>
> [FSCK] Unreachable nat entries [Ok..] [0x0]
> [FSCK] SIT valid block bitmap checking [Ok..]
> [FSCK] Hard link checking for regular file [Ok..] [0x50c]
> [FSCK] valid_block_count matching with CP [Ok..]
> [0x9589819]
> [FSCK] valid_node_count matching with CP (de lookup) [Ok..] [0x2bec97]
> [FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x2bec97]
> [FSCK] valid_inode_count matched with CP [Ok..] [0x29f985]
> [FSCK] free segment_count matched with CP [Ok..] [0x18105]
> [FSCK] next block offset is free [Ok..]
> [FSCK] fixing SIT types
> [FSCK] other corrupted bugs [Ok..]
>
> Done: 263.250850 secs
>
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-10-30 9:06 ` Chao Yu
@ 2020-10-30 11:10 ` kitestramuort
2020-10-31 9:09 ` kitestramuort
0 siblings, 1 reply; 10+ messages in thread
From: kitestramuort @ 2020-10-30 11:10 UTC (permalink / raw)
To: Chao Yu, linux-f2fs-devel
On Fri, 2020-10-30 at 17:06 +0800, Chao Yu wrote:
> On 2020/10/30 16:56, kitestramuort wrote:
>
>
> It doesn't print function name in callstack, could you check your
> linker option, I guess it needs to add -rdynamic option? not sure.
Apologies. The correct call trace and fsck follow. I just realised that
the error happens the moment I open Firefox
F2FS-fs (nvme0n1p4): access invalid blkaddr:1598541474
[ 25.725898] ------------[ cut here ]------------
[ 25.725903] WARNING: CPU: 6 PID: 2018 at
f2fs_is_valid_blkaddr+0x23a/0x250
[ 25.725904] Modules linked in: r8168(O)
[ 25.725908] CPU: 6 PID: 2018 Comm: Cache2 I/O Tainted: G S U O
5.10.0-rc1-S #10
[ 25.725909] Hardware name: 51NB X213s/X213s, BIOS 4.12-3653-
gb544fe48af-dirty 10/29/2020
[ 25.725912] RIP: 0010:f2fs_is_valid_blkaddr+0x23a/0x250
[ 25.725913] Code: 01 c8 39 c6 73 09 41 8b 42 5c e9 26 fe ff ff 89 f2
48 c7 c6 ad f1 5c 9a 48 89 3c 24 e8 4a 62 7d 00 48 8b 3c 24 f0 80 4f 48
04 <0f> 0b 31 c0 e9 af fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66 90
[ 25.725915] RSP: 0018:ffffb43302cbf8e0 EFLAGS: 00010206
[ 25.725916] RAX: 0000000000000036 RBX: 0000000000000369 RCX:
0000000000000000
[ 25.725917] RDX: ffff96592f5a5920 RSI: ffff96592f5977c0 RDI:
ffff9655c0cdf000
[ 25.725918] RBP: ffff9655c2334700 R08: ffffffff9aa14c48 R09:
00000000ffffffea
[ 25.725919] R10: 00000000ffffbfff R11: 80000000ffffc000 R12:
0000000000000001
[ 25.725919] R13: ffff9656063e95b8 R14: 0000000000000003 R15:
0000000000001000
[ 25.725921] FS: 00007f7cf1930640(0000) GS:ffff96592f580000(0000)
knlGS:0000000000000000
[ 25.725922] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 25.725923] CR2: 00007f7cef899485 CR3: 00000001028a4006 CR4:
00000000001706e0
[ 25.725923] Call Trace:
[ 25.725927] ? f2fs_llseek+0x204/0x620
[ 25.725929] ? ovl_copy_up_data+0x14f/0x200
[ 25.725931] ? ovl_copy_up_inode+0x174/0x1e0
[ 25.725933] ? ovl_copy_up_one+0xa22/0xdf0
[ 25.725936] ? ovl_copy_up_flags+0xa6/0xf0
[ 25.725938] ? ovl_aio_cleanup_handler+0xd0/0xd0
[ 25.725939] ? ovl_maybe_copy_up+0x86/0xa0
[ 25.725941] ? ovl_open+0x22/0x80
[ 25.725943] ? do_dentry_open+0x136/0x350
[ 25.725945] ? path_openat+0xb7e/0xf40
[ 25.725947] ? __check_sticky+0x40/0x40
[ 25.725948] ? do_filp_open+0x70/0x100
[ 25.725950] ? __check_sticky+0x40/0x40
[ 25.725951] ? __check_sticky+0x40/0x40
[ 25.725953] ? __x64_sys_openat+0x1db/0x2c0
[ 25.725955] ? do_syscall_64+0x2d/0x40
[ 25.725957] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 25.725959] CPU: 6 PID: 2018 Comm: Cache2 I/O Tainted: G S U O
5.10.0-rc1-S #10
[ 25.725959] Hardware name: 51NB X213s/X213s, BIOS 4.12-3653-
gb544fe48af-dirty 10/29/2020
[ 25.725960] Call Trace:
[ 25.725962] ? dump_stack+0x58/0x6b
[ 25.725964] ? __warn.cold+0x24/0x74
[ 25.725966] ? f2fs_is_valid_blkaddr+0x23a/0x250
[ 25.725968] ? report_bug+0x136/0x170
[ 25.725969] ? handle_bug+0x3c/0x60
[ 25.725971] ? exc_invalid_op+0x18/0x150
[ 25.725972] ? asm_exc_invalid_op+0xf/0x20
[ 25.725974] ? f2fs_is_valid_blkaddr+0x23a/0x250
[ 25.725976] ? f2fs_llseek+0x204/0x620
[ 25.725978] ? ovl_copy_up_data+0x14f/0x200
[ 25.725980] ? ovl_copy_up_inode+0x174/0x1e0
[ 25.725981] ? ovl_copy_up_one+0xa22/0xdf0
[ 25.725984] ? ovl_copy_up_flags+0xa6/0xf0
[ 25.725986] ? ovl_aio_cleanup_handler+0xd0/0xd0
[ 25.725987] ? ovl_maybe_copy_up+0x86/0xa0
[ 25.725989] ? ovl_open+0x22/0x80
[ 25.725990] ? do_dentry_open+0x136/0x350
[ 25.725991] ? path_openat+0xb7e/0xf40
[ 25.725993] ? __check_sticky+0x40/0x40
[ 25.725995] ? do_filp_open+0x70/0x100
[ 25.725996] ? __check_sticky+0x40/0x40
[ 25.725998] ? __check_sticky+0x40/0x40
[ 25.725999] ? __x64_sys_openat+0x1db/0x2c0
[ 25.726000] ? do_syscall_64+0x2d/0x40
[ 25.726001] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
[ 25.726003] ---[ end trace 3ad187bffec8b173 ]---
and fsck dry run with the last version:
Info: Dry run
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 1692427663 (826380 MB)
Info: MKFS version
"Linux version 4.20.0-arch1-1-ARCH (builduser@heftig-29859) (gcc
version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC
2018"
Info: FSCK version
from "Linux version 5.2.5-arch1-1-ARCH (builduser@heftig-118908) (gcc
version 9.1.0 (GCC)) #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019"
to "Linux version 5.10.0-rc1-S (root@x210) (gcc (GCC) 10.2.0, GNU
ld (GNU Binutils) 2.35.1) #10 SMP PREEMPT Fri Oct 30 12:00:34 CET 2020"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt =
00000000000000000000000000000000
Info: total FS sectors = 1692427656 (826380 MB)
Info: CKPT version = 284790b
Info: checkpoint state = 55 : crc fsck compacted_summary unmount
[FSCK] Unreachable nat entries [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking [Ok..]
[FSCK] Hard link checking for regular file [Ok..] [0x50c]
[FSCK] valid_block_count matching with CP [Ok..]
[0x958a824]
[FSCK] valid_node_count matching with CP (de lookup) [Ok..] [0x2bec75]
[FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x2bec75]
[FSCK] valid_inode_count matched with CP [Ok..] [0x29f961]
[FSCK] free segment_count matched with CP [Ok..] [0x180e2]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Ok..]
Done: 108.720284 secs
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-10-30 11:10 ` kitestramuort
@ 2020-10-31 9:09 ` kitestramuort
2020-11-02 9:39 ` Chao Yu
0 siblings, 1 reply; 10+ messages in thread
From: kitestramuort @ 2020-10-31 9:09 UTC (permalink / raw)
To: Chao Yu, linux-f2fs-devel
I believe that the error is triggered by the overlayfs. I use this tool
to manage browsers' profiles in the tmpfs which uses Overlayfs
https://wiki.archlinux.org/index.php/Profile-sync-daemon
If I turn it off and launch Firefox the error does not show, but it
always does if it's on.
On Fri, 2020-10-30 at 12:10 +0100, kitestramuort wrote:
> On Fri, 2020-10-30 at 17:06 +0800, Chao Yu wrote:
> > On 2020/10/30 16:56, kitestramuort wrote:
> >
> >
> > It doesn't print function name in callstack, could you check your
> > linker option, I guess it needs to add -rdynamic option? not sure.
>
> Apologies. The correct call trace and fsck follow. I just realised
> that
> the error happens the moment I open Firefox
>
> F2FS-fs (nvme0n1p4): access invalid blkaddr:1598541474
> [ 25.725898] ------------[ cut here ]------------
> [ 25.725903] WARNING: CPU: 6 PID: 2018 at
> f2fs_is_valid_blkaddr+0x23a/0x250
> [ 25.725904] Modules linked in: r8168(O)
> [ 25.725908] CPU: 6 PID: 2018 Comm: Cache2 I/O Tainted: G S U
> O
> 5.10.0-rc1-S #10
> [ 25.725909] Hardware name: 51NB X213s/X213s, BIOS 4.12-3653-
> gb544fe48af-dirty 10/29/2020
> [ 25.725912] RIP: 0010:f2fs_is_valid_blkaddr+0x23a/0x250
> [ 25.725913] Code: 01 c8 39 c6 73 09 41 8b 42 5c e9 26 fe ff ff 89
> f2
> 48 c7 c6 ad f1 5c 9a 48 89 3c 24 e8 4a 62 7d 00 48 8b 3c 24 f0 80 4f
> 48
> 04 <0f> 0b 31 c0 e9 af fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66
> 90
> [ 25.725915] RSP: 0018:ffffb43302cbf8e0 EFLAGS: 00010206
> [ 25.725916] RAX: 0000000000000036 RBX: 0000000000000369 RCX:
> 0000000000000000
> [ 25.725917] RDX: ffff96592f5a5920 RSI: ffff96592f5977c0 RDI:
> ffff9655c0cdf000
> [ 25.725918] RBP: ffff9655c2334700 R08: ffffffff9aa14c48 R09:
> 00000000ffffffea
> [ 25.725919] R10: 00000000ffffbfff R11: 80000000ffffc000 R12:
> 0000000000000001
> [ 25.725919] R13: ffff9656063e95b8 R14: 0000000000000003 R15:
> 0000000000001000
> [ 25.725921] FS: 00007f7cf1930640(0000) GS:ffff96592f580000(0000)
> knlGS:0000000000000000
> [ 25.725922] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [ 25.725923] CR2: 00007f7cef899485 CR3: 00000001028a4006 CR4:
> 00000000001706e0
> [ 25.725923] Call Trace:
> [ 25.725927] ? f2fs_llseek+0x204/0x620
> [ 25.725929] ? ovl_copy_up_data+0x14f/0x200
> [ 25.725931] ? ovl_copy_up_inode+0x174/0x1e0
> [ 25.725933] ? ovl_copy_up_one+0xa22/0xdf0
> [ 25.725936] ? ovl_copy_up_flags+0xa6/0xf0
> [ 25.725938] ? ovl_aio_cleanup_handler+0xd0/0xd0
> [ 25.725939] ? ovl_maybe_copy_up+0x86/0xa0
> [ 25.725941] ? ovl_open+0x22/0x80
> [ 25.725943] ? do_dentry_open+0x136/0x350
> [ 25.725945] ? path_openat+0xb7e/0xf40
> [ 25.725947] ? __check_sticky+0x40/0x40
> [ 25.725948] ? do_filp_open+0x70/0x100
> [ 25.725950] ? __check_sticky+0x40/0x40
> [ 25.725951] ? __check_sticky+0x40/0x40
> [ 25.725953] ? __x64_sys_openat+0x1db/0x2c0
> [ 25.725955] ? do_syscall_64+0x2d/0x40
> [ 25.725957] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 25.725959] CPU: 6 PID: 2018 Comm: Cache2 I/O Tainted: G S U
> O
> 5.10.0-rc1-S #10
> [ 25.725959] Hardware name: 51NB X213s/X213s, BIOS 4.12-3653-
> gb544fe48af-dirty 10/29/2020
> [ 25.725960] Call Trace:
> [ 25.725962] ? dump_stack+0x58/0x6b
> [ 25.725964] ? __warn.cold+0x24/0x74
> [ 25.725966] ? f2fs_is_valid_blkaddr+0x23a/0x250
> [ 25.725968] ? report_bug+0x136/0x170
> [ 25.725969] ? handle_bug+0x3c/0x60
> [ 25.725971] ? exc_invalid_op+0x18/0x150
> [ 25.725972] ? asm_exc_invalid_op+0xf/0x20
> [ 25.725974] ? f2fs_is_valid_blkaddr+0x23a/0x250
> [ 25.725976] ? f2fs_llseek+0x204/0x620
> [ 25.725978] ? ovl_copy_up_data+0x14f/0x200
> [ 25.725980] ? ovl_copy_up_inode+0x174/0x1e0
> [ 25.725981] ? ovl_copy_up_one+0xa22/0xdf0
> [ 25.725984] ? ovl_copy_up_flags+0xa6/0xf0
> [ 25.725986] ? ovl_aio_cleanup_handler+0xd0/0xd0
> [ 25.725987] ? ovl_maybe_copy_up+0x86/0xa0
> [ 25.725989] ? ovl_open+0x22/0x80
> [ 25.725990] ? do_dentry_open+0x136/0x350
> [ 25.725991] ? path_openat+0xb7e/0xf40
> [ 25.725993] ? __check_sticky+0x40/0x40
> [ 25.725995] ? do_filp_open+0x70/0x100
> [ 25.725996] ? __check_sticky+0x40/0x40
> [ 25.725998] ? __check_sticky+0x40/0x40
> [ 25.725999] ? __x64_sys_openat+0x1db/0x2c0
> [ 25.726000] ? do_syscall_64+0x2d/0x40
> [ 25.726001] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
> [ 25.726003] ---[ end trace 3ad187bffec8b173 ]---
>
>
> and fsck dry run with the last version:
>
> Info: Dry run
> Info: Segments per section = 1
> Info: Sections per zone = 1
> Info: sector size = 512
> Info: total sectors = 1692427663 (826380 MB)
> Info: MKFS version
> "Linux version 4.20.0-arch1-1-ARCH (builduser@heftig-29859) (gcc
> version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC
> 2018"
> Info: FSCK version
> from "Linux version 5.2.5-arch1-1-ARCH (builduser@heftig-118908)
> (gcc
> version 9.1.0 (GCC)) #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019"
> to "Linux version 5.10.0-rc1-S (root@x210) (gcc (GCC) 10.2.0, GNU
> ld (GNU Binutils) 2.35.1) #10 SMP PREEMPT Fri Oct 30 12:00:34 CET
> 2020"
> Info: superblock features = 0 :
> Info: superblock encrypt level = 0, salt =
> 00000000000000000000000000000000
> Info: total FS sectors = 1692427656 (826380 MB)
> Info: CKPT version = 284790b
> Info: checkpoint state = 55 : crc fsck compacted_summary unmount
>
> [FSCK] Unreachable nat entries [Ok..] [0x0]
> [FSCK] SIT valid block bitmap checking [Ok..]
> [FSCK] Hard link checking for regular file [Ok..] [0x50c]
> [FSCK] valid_block_count matching with CP [Ok..]
> [0x958a824]
> [FSCK] valid_node_count matching with CP (de lookup) [Ok..]
> [0x2bec75]
> [FSCK] valid_node_count matching with CP (nat lookup) [Ok..]
> [0x2bec75]
> [FSCK] valid_inode_count matched with CP [Ok..]
> [0x29f961]
> [FSCK] free segment_count matched with CP [Ok..]
> [0x180e2]
> [FSCK] next block offset is free [Ok..]
> [FSCK] fixing SIT types
> [FSCK] other corrupted bugs [Ok..]
>
> Done: 108.720284 secs
>
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-10-31 9:09 ` kitestramuort
@ 2020-11-02 9:39 ` Chao Yu
2020-11-02 9:55 ` kitestramuort
0 siblings, 1 reply; 10+ messages in thread
From: Chao Yu @ 2020-11-02 9:39 UTC (permalink / raw)
To: kitestramuort, linux-f2fs-devel
On 2020/10/31 17:09, kitestramuort wrote:
> I believe that the error is triggered by the overlayfs. I use this tool
> to manage browsers' profiles in the tmpfs which uses Overlayfs
> https://wiki.archlinux.org/index.php/Profile-sync-daemon
I found one case which can cause this incorrect report from llseek(),
could you please have a try with patch I just sent?
[PATCH] f2fs: fix to seek incorrect data offset in inline data file
Thanks,
>
> If I turn it off and launch Firefox the error does not show, but it
> always does if it's on.
>
>
> On Fri, 2020-10-30 at 12:10 +0100, kitestramuort wrote:
>> On Fri, 2020-10-30 at 17:06 +0800, Chao Yu wrote:
>>> On 2020/10/30 16:56, kitestramuort wrote:
>>>
>>>
>>> It doesn't print function name in callstack, could you check your
>>> linker option, I guess it needs to add -rdynamic option? not sure.
>>
>> Apologies. The correct call trace and fsck follow. I just realised
>> that
>> the error happens the moment I open Firefox
>>
>> F2FS-fs (nvme0n1p4): access invalid blkaddr:1598541474
>> [ 25.725898] ------------[ cut here ]------------
>> [ 25.725903] WARNING: CPU: 6 PID: 2018 at
>> f2fs_is_valid_blkaddr+0x23a/0x250
>> [ 25.725904] Modules linked in: r8168(O)
>> [ 25.725908] CPU: 6 PID: 2018 Comm: Cache2 I/O Tainted: G S U
>> O
>> 5.10.0-rc1-S #10
>> [ 25.725909] Hardware name: 51NB X213s/X213s, BIOS 4.12-3653-
>> gb544fe48af-dirty 10/29/2020
>> [ 25.725912] RIP: 0010:f2fs_is_valid_blkaddr+0x23a/0x250
>> [ 25.725913] Code: 01 c8 39 c6 73 09 41 8b 42 5c e9 26 fe ff ff 89
>> f2
>> 48 c7 c6 ad f1 5c 9a 48 89 3c 24 e8 4a 62 7d 00 48 8b 3c 24 f0 80 4f
>> 48
>> 04 <0f> 0b 31 c0 e9 af fe ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 66
>> 90
>> [ 25.725915] RSP: 0018:ffffb43302cbf8e0 EFLAGS: 00010206
>> [ 25.725916] RAX: 0000000000000036 RBX: 0000000000000369 RCX:
>> 0000000000000000
>> [ 25.725917] RDX: ffff96592f5a5920 RSI: ffff96592f5977c0 RDI:
>> ffff9655c0cdf000
>> [ 25.725918] RBP: ffff9655c2334700 R08: ffffffff9aa14c48 R09:
>> 00000000ffffffea
>> [ 25.725919] R10: 00000000ffffbfff R11: 80000000ffffc000 R12:
>> 0000000000000001
>> [ 25.725919] R13: ffff9656063e95b8 R14: 0000000000000003 R15:
>> 0000000000001000
>> [ 25.725921] FS: 00007f7cf1930640(0000) GS:ffff96592f580000(0000)
>> knlGS:0000000000000000
>> [ 25.725922] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
>> [ 25.725923] CR2: 00007f7cef899485 CR3: 00000001028a4006 CR4:
>> 00000000001706e0
>> [ 25.725923] Call Trace:
>> [ 25.725927] ? f2fs_llseek+0x204/0x620
>> [ 25.725929] ? ovl_copy_up_data+0x14f/0x200
>> [ 25.725931] ? ovl_copy_up_inode+0x174/0x1e0
>> [ 25.725933] ? ovl_copy_up_one+0xa22/0xdf0
>> [ 25.725936] ? ovl_copy_up_flags+0xa6/0xf0
>> [ 25.725938] ? ovl_aio_cleanup_handler+0xd0/0xd0
>> [ 25.725939] ? ovl_maybe_copy_up+0x86/0xa0
>> [ 25.725941] ? ovl_open+0x22/0x80
>> [ 25.725943] ? do_dentry_open+0x136/0x350
>> [ 25.725945] ? path_openat+0xb7e/0xf40
>> [ 25.725947] ? __check_sticky+0x40/0x40
>> [ 25.725948] ? do_filp_open+0x70/0x100
>> [ 25.725950] ? __check_sticky+0x40/0x40
>> [ 25.725951] ? __check_sticky+0x40/0x40
>> [ 25.725953] ? __x64_sys_openat+0x1db/0x2c0
>> [ 25.725955] ? do_syscall_64+0x2d/0x40
>> [ 25.725957] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
>> [ 25.725959] CPU: 6 PID: 2018 Comm: Cache2 I/O Tainted: G S U
>> O
>> 5.10.0-rc1-S #10
>> [ 25.725959] Hardware name: 51NB X213s/X213s, BIOS 4.12-3653-
>> gb544fe48af-dirty 10/29/2020
>> [ 25.725960] Call Trace:
>> [ 25.725962] ? dump_stack+0x58/0x6b
>> [ 25.725964] ? __warn.cold+0x24/0x74
>> [ 25.725966] ? f2fs_is_valid_blkaddr+0x23a/0x250
>> [ 25.725968] ? report_bug+0x136/0x170
>> [ 25.725969] ? handle_bug+0x3c/0x60
>> [ 25.725971] ? exc_invalid_op+0x18/0x150
>> [ 25.725972] ? asm_exc_invalid_op+0xf/0x20
>> [ 25.725974] ? f2fs_is_valid_blkaddr+0x23a/0x250
>> [ 25.725976] ? f2fs_llseek+0x204/0x620
>> [ 25.725978] ? ovl_copy_up_data+0x14f/0x200
>> [ 25.725980] ? ovl_copy_up_inode+0x174/0x1e0
>> [ 25.725981] ? ovl_copy_up_one+0xa22/0xdf0
>> [ 25.725984] ? ovl_copy_up_flags+0xa6/0xf0
>> [ 25.725986] ? ovl_aio_cleanup_handler+0xd0/0xd0
>> [ 25.725987] ? ovl_maybe_copy_up+0x86/0xa0
>> [ 25.725989] ? ovl_open+0x22/0x80
>> [ 25.725990] ? do_dentry_open+0x136/0x350
>> [ 25.725991] ? path_openat+0xb7e/0xf40
>> [ 25.725993] ? __check_sticky+0x40/0x40
>> [ 25.725995] ? do_filp_open+0x70/0x100
>> [ 25.725996] ? __check_sticky+0x40/0x40
>> [ 25.725998] ? __check_sticky+0x40/0x40
>> [ 25.725999] ? __x64_sys_openat+0x1db/0x2c0
>> [ 25.726000] ? do_syscall_64+0x2d/0x40
>> [ 25.726001] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9
>> [ 25.726003] ---[ end trace 3ad187bffec8b173 ]---
>>
>>
>> and fsck dry run with the last version:
>>
>> Info: Dry run
>> Info: Segments per section = 1
>> Info: Sections per zone = 1
>> Info: sector size = 512
>> Info: total sectors = 1692427663 (826380 MB)
>> Info: MKFS version
>> "Linux version 4.20.0-arch1-1-ARCH (builduser@heftig-29859) (gcc
>> version 8.2.1 20181127 (GCC)) #1 SMP PREEMPT Mon Dec 24 03:00:40 UTC
>> 2018"
>> Info: FSCK version
>> from "Linux version 5.2.5-arch1-1-ARCH (builduser@heftig-118908)
>> (gcc
>> version 9.1.0 (GCC)) #1 SMP PREEMPT Wed Jul 31 08:30:34 UTC 2019"
>> to "Linux version 5.10.0-rc1-S (root@x210) (gcc (GCC) 10.2.0, GNU
>> ld (GNU Binutils) 2.35.1) #10 SMP PREEMPT Fri Oct 30 12:00:34 CET
>> 2020"
>> Info: superblock features = 0 :
>> Info: superblock encrypt level = 0, salt =
>> 00000000000000000000000000000000
>> Info: total FS sectors = 1692427656 (826380 MB)
>> Info: CKPT version = 284790b
>> Info: checkpoint state = 55 : crc fsck compacted_summary unmount
>>
>> [FSCK] Unreachable nat entries [Ok..] [0x0]
>> [FSCK] SIT valid block bitmap checking [Ok..]
>> [FSCK] Hard link checking for regular file [Ok..] [0x50c]
>> [FSCK] valid_block_count matching with CP [Ok..]
>> [0x958a824]
>> [FSCK] valid_node_count matching with CP (de lookup) [Ok..]
>> [0x2bec75]
>> [FSCK] valid_node_count matching with CP (nat lookup) [Ok..]
>> [0x2bec75]
>> [FSCK] valid_inode_count matched with CP [Ok..]
>> [0x29f961]
>> [FSCK] free segment_count matched with CP [Ok..]
>> [0x180e2]
>> [FSCK] next block offset is free [Ok..]
>> [FSCK] fixing SIT types
>> [FSCK] other corrupted bugs [Ok..]
>>
>> Done: 108.720284 secs
>>
>>
>>
>> _______________________________________________
>> Linux-f2fs-devel mailing list
>> Linux-f2fs-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
>
>
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-11-02 9:39 ` Chao Yu
@ 2020-11-02 9:55 ` kitestramuort
2020-11-02 10:20 ` Chao Yu
0 siblings, 1 reply; 10+ messages in thread
From: kitestramuort @ 2020-11-02 9:55 UTC (permalink / raw)
To: Chao Yu, linux-f2fs-devel
On Mon, 2020-11-02 at 17:39 +0800, Chao Yu wrote:
> On 2020/10/31 17:09, kitestramuort wrote:
> > I believe that the error is triggered by the overlayfs. I use this
> > tool
> > to manage browsers' profiles in the tmpfs which uses Overlayfs
> > https://wiki.archlinux.org/index.php/Profile-sync-daemon
>
> I found one case which can cause this incorrect report from llseek(),
> could you please have a try with patch I just sent?
>
> [PATCH] f2fs: fix to seek incorrect data offset in inline data file
>
> Thanks,
That fixes it. Thank you very much!
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-11-02 9:55 ` kitestramuort
@ 2020-11-02 10:20 ` Chao Yu
2020-11-02 10:30 ` kitestramuort
0 siblings, 1 reply; 10+ messages in thread
From: Chao Yu @ 2020-11-02 10:20 UTC (permalink / raw)
To: kitestramuort, linux-f2fs-devel
On 2020/11/2 17:55, kitestramuort wrote:
> On Mon, 2020-11-02 at 17:39 +0800, Chao Yu wrote:
>> On 2020/10/31 17:09, kitestramuort wrote:
>>> I believe that the error is triggered by the overlayfs. I use this
>>> tool
>>> to manage browsers' profiles in the tmpfs which uses Overlayfs
>>> https://wiki.archlinux.org/index.php/Profile-sync-daemon
>>
>> I found one case which can cause this incorrect report from llseek(),
>> could you please have a try with patch I just sent?
>>
>> [PATCH] f2fs: fix to seek incorrect data offset in inline data file
>>
>> Thanks,
>
>
> That fixes it. Thank you very much!
Thanks for the quick test. :)
If you don't mind, I will change tag from Reported-by to Reported-and-tested-by
in the patch.
Thanks,
>
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
* Re: [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr
2020-11-02 10:20 ` Chao Yu
@ 2020-11-02 10:30 ` kitestramuort
0 siblings, 0 replies; 10+ messages in thread
From: kitestramuort @ 2020-11-02 10:30 UTC (permalink / raw)
To: Chao Yu, linux-f2fs-devel
On Mon, 2020-11-02 at 18:20 +0800, Chao Yu wrote:
> >
> > That fixes it. Thank you very much!
>
> Thanks for the quick test. :)
>
> If you don't mind, I will change tag from Reported-by to Reported-
> and-tested-by
> in the patch.
>
> Thanks,
No problem, although I am only one small use case.
Thanks again
cheers
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2020-11-02 10:30 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-10-29 16:40 [f2fs-dev] Linux 5.10-rc1: F2FS-fs access invalid blkaddr kitestramuort
2020-10-30 1:50 ` Chao Yu
2020-10-30 8:56 ` kitestramuort
2020-10-30 9:06 ` Chao Yu
2020-10-30 11:10 ` kitestramuort
2020-10-31 9:09 ` kitestramuort
2020-11-02 9:39 ` Chao Yu
2020-11-02 9:55 ` kitestramuort
2020-11-02 10:20 ` Chao Yu
2020-11-02 10:30 ` kitestramuort
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.