* Re: [f2fs-dev] f2fs write error Linux v6.2
[not found] ` <Y6bz4wOC0nwu2yGU@debian.me>
@ 2022-12-24 14:00 ` Bagas Sanjaya
2022-12-30 4:04 ` [f2fs-dev] Fwd: " Jeff Chua
0 siblings, 1 reply; 10+ messages in thread
From: Bagas Sanjaya @ 2022-12-24 14:00 UTC (permalink / raw)
To: Jeff Chua, lkml, Jaegeuk Kim, Chao Yu, F2FS Development,
Linux Regressions
On 12/24/22 19:43, Bagas Sanjaya wrote:
> On Sat, Dec 24, 2022 at 01:48:55PM +0800, Jeff Chua wrote:
>> Got the following error in latest linux-6.2-git with just vim (:w
>> file1). No problem with linux-6.1.1
>>
>> 2022-12-22T14:09:51.419409+08:00 [localhost] kernel: BUG: kernel NULL
>> pointer dereference, address: 0000000000000024
>> 2022-12-22T14:09:51.419422+08:00 [localhost] kernel: #PF: supervisor
>> write access in kernel mode
>> 2022-12-22T14:09:51.419423+08:00 [localhost] kernel: #PF:
>> error_code(0x0002) - not-present page
>> 2022-12-22T14:09:51.419424+08:00 [localhost] kernel: PGD 147b63067 P4D
>> 147b63067 PUD 177d5c067 PMD 0
>> 2022-12-22T14:09:51.419424+08:00 [localhost] kernel: Oops: 0002 [#7] PREEMPT SMP
>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: CPU: 6 PID: 22891
>> Comm: vi Tainted: G UD 6.1.0 #11
>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: Hardware name:
>> LENOVO 21CCS1GL00/21CCS1GL00, BIOS N3AET69W (1.34 ) 12/05/2022
>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: RIP:
>> 0010:f2fs_issue_flush+0x10e/0x180
>> 2022-12-22T14:09:51.419429+08:00 [localhost] kernel: Code: ba 01 00 00
>> 00 be 03 00 00 00 e8 ad e8 d5 ff 48 83 3b 00 74 1e 48 89 e7 e8 7f c1
>> 84 00 f0 ff 4b 24 8b 44 24 2c e9 66 ff ff ff <f0> ff 43 24 e9 4a ff ff
>> ff 45 31 ff 4c 87 7b 28 4d 85 ff 74 d6 44
>> 2022-12-22T14:09:51.419429+08:00 [localhost] kernel: RSP:
>> 0018:ffffc90000b13df0 EFLAGS: 00010246
>> 2022-12-22T14:09:51.419430+08:00 [localhost] kernel: RAX:
>> ffff888101caccc0 RBX: 0000000000000000 RCX: 0000000000000000
>> 2022-12-22T14:09:51.419430+08:00 [localhost] kernel: RDX:
>> 0000000010000088 RSI: 000000000005a844 RDI: ffff8881027bf000
>> 2022-12-22T14:09:51.419431+08:00 [localhost] kernel: RBP:
>> ffff8881027bf000 R08: 0000000000000000 R09: ffff8881027bf2a8
>> 2022-12-22T14:09:51.419431+08:00 [localhost] kernel: R10:
>> 0000000000000000 R11: 0000000000000000 R12: 0000000000000024
>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: R13:
>> 000000000005a844 R14: 000000000005a844 R15: 0000000000000000
>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: FS:
>> 00007ff03fdf0b80(0000) GS:ffff88883f380000(0000)
>> knlGS:0000000000000000
>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: CS: 0010 DS:
>> 0000 ES: 0000 CR0: 0000000080050033
>> 2022-12-22T14:09:51.419433+08:00 [localhost] kernel: CR2:
>> 0000000000000024 CR3: 000000013d64e006 CR4: 0000000000770ee0
>> 2022-12-22T14:09:51.419433+08:00 [localhost] kernel: PKRU: 55555554
>> 2022-12-22T14:09:51.419434+08:00 [localhost] kernel: Call Trace:
>> 2022-12-22T14:09:51.419434+08:00 [localhost] kernel: <TASK>
>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>> preempt_count_add+0x63/0x90
>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>> preempt_count_add+0x63/0x90
>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>> preempt_count_add+0x63/0x90
>> 2022-12-22T14:09:51.419436+08:00 [localhost] kernel:
>> f2fs_do_sync_file+0x489/0x650
>> 2022-12-22T14:09:51.419436+08:00 [localhost] kernel: __x64_sys_fsync+0x2f/0x60
>> 2022-12-22T14:09:51.419437+08:00 [localhost] kernel: do_syscall_64+0x35/0x80
>> 2022-12-22T14:09:51.419437+08:00 [localhost] kernel:
>> entry_SYSCALL_64_after_hwframe+0x46/0xb0
>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: RIP: 0033:0x7ff03feef20b
>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: Code: 3d 00 f0 ff
>> ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 a3 a2 f8
>> ff 8b 7c 24 0c 41 89 c0 b8 4a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35
>> 44 89 c7 89 44 24 0c e8 01 a3 f8 ff 8b 44
>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: RSP:
>> 002b:00007ffe6ecca530 EFLAGS: 00000293 ORIG_RAX: 000000000000004a
>> 2022-12-22T14:09:51.419439+08:00 [localhost] kernel: RAX:
>> ffffffffffffffda RBX: 0000000000000001 RCX: 00007ff03feef20b
>> 2022-12-22T14:09:51.419439+08:00 [localhost] kernel: RDX:
>> 0000000000000002 RSI: 0000000000000002 RDI: 0000000000000003
>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: RBP:
>> 0000000000002000 R08: 0000000000000000 R09: 00000000024bcfb0
>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: R10:
>> fffffffffffff4bf R11: 0000000000000293 R12: 00000000000006b7
>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: R13:
>> 000000000000003d R14: 0000000000000000 R15: 00000000024a1680
>> 2022-12-22T14:09:51.419441+08:00 [localhost] kernel: </TASK>
>> 2022-12-22T14:09:51.419441+08:00 [localhost] kernel: Modules linked
>> in: [last unloaded: ecc]
>> 2022-12-22T14:09:51.419442+08:00 [localhost] kernel: CR2: 0000000000000024
>> 2022-12-22T14:09:51.419442+08:00 [localhost] kernel: ---[ end trace
>> 0000000000000000 ]---
>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: RIP:
>> 0010:f2fs_issue_flush+0x10e/0x180
>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: Code: ba 01 00 00
>> 00 be 03 00 00 00 e8 ad e8 d5 ff 48 83 3b 00 74 1e 48 89 e7 e8 7f c1
>> 84 00 f0 ff 4b 24 8b 44 24 2c e9 66 ff ff ff <f0> ff 43 24 e9 4a ff ff
>> ff 45 31 ff 4c 87 7b 28 4d 85 ff 74 d6 44
>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: RSP:
>> 0018:ffffc90003903df0 EFLAGS: 00010246
>> 2022-12-22T14:09:51.419444+08:00 [localhost] kernel: RAX:
>> ffff888100106d80 RBX: 0000000000000000 RCX: 0000000000000000
>> 2022-12-22T14:09:51.419444+08:00 [localhost] kernel: RDX:
>> 0000000010000088 RSI: 0000000000b0e2ba RDI: ffff888116227000
>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: RBP:
>> ffff888116227000 R08: 0000000000000000 R09: ffff8881162272a8
>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: R10:
>> 0000000000000000 R11: 0000000000000000 R12: 0000000000000024
>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: R13:
>> 0000000000b0e2ba R14: 0000000000b0e2ba R15: 0000000000000000
>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: FS:
>> 00007ff03fdf0b80(0000) GS:ffff88883f380000(0000)
>> knlGS:0000000000000000
>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: CS: 0010 DS:
>> 0000 ES: 0000 CR0: 0000000080050033
>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: CR2:
>> 0000000000000024 CR3: 000000013d64e006 CR4: 0000000000770ee0
>> 2022-12-22T14:09:51.419447+08:00 [localhost] kernel: PKRU: 55555554
>
> Thanks for the report! I'm adding this to regzbot:
>
> #regzbot ^introduced v6.1.1..v6.2
> #regzbot title f2fs: kernel NULL pointer dereference when writing file
>
Oops, I mean:
#regzbot introduced v6.1.1..72a85e2b0a1e1e
Also, Cc'ed other F2FS maintainers and relevant lists.
Thanks.
--
An old man doll... just what I always wanted! - Clara
_______________________________________________
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
* [f2fs-dev] Fwd: f2fs write error Linux v6.2
2022-12-24 14:00 ` [f2fs-dev] f2fs write error Linux v6.2 Bagas Sanjaya
@ 2022-12-30 4:04 ` Jeff Chua
2022-12-30 5:56 ` Thorsten Leemhuis
0 siblings, 1 reply; 10+ messages in thread
From: Jeff Chua @ 2022-12-30 4:04 UTC (permalink / raw)
To: lkml, Linus Torvalds, Bagas Sanjaya, Jaegeuk Kim, Chao Yu,
F2FS Development, Linux Regressions
On 12/24/22 19:43, Bagas Sanjaya wrote:
> On Sat, Dec 24, 2022 at 01:48:55PM +0800, Jeff Chua wrote:
>> Got the following error in latest linux-6.2-git with just vim (:w
>> file1). No problem with linux-6.1.1
What happened to the f2fs developers? No response from anyone yet. Am
I the only one facing this? Linux-6.2 is unusable until this is fixed.
What can I do to help?
Jeff
>> 2022-12-22T14:09:51.419409+08:00 [localhost] kernel: BUG: kernel NULL
>> pointer dereference, address: 0000000000000024
>> 2022-12-22T14:09:51.419422+08:00 [localhost] kernel: #PF: supervisor
>> write access in kernel mode
>> 2022-12-22T14:09:51.419423+08:00 [localhost] kernel: #PF:
>> error_code(0x0002) - not-present page
>> 2022-12-22T14:09:51.419424+08:00 [localhost] kernel: PGD 147b63067 P4D
>> 147b63067 PUD 177d5c067 PMD 0
>> 2022-12-22T14:09:51.419424+08:00 [localhost] kernel: Oops: 0002 [#7] PREEMPT SMP
>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: CPU: 6 PID: 22891
>> Comm: vi Tainted: G UD 6.1.0 #11
>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: Hardware name:
>> LENOVO 21CCS1GL00/21CCS1GL00, BIOS N3AET69W (1.34 ) 12/05/2022
>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: RIP:
>> 0010:f2fs_issue_flush+0x10e/0x180
>> 2022-12-22T14:09:51.419429+08:00 [localhost] kernel: Code: ba 01 00 00
>> 00 be 03 00 00 00 e8 ad e8 d5 ff 48 83 3b 00 74 1e 48 89 e7 e8 7f c1
>> 84 00 f0 ff 4b 24 8b 44 24 2c e9 66 ff ff ff <f0> ff 43 24 e9 4a ff ff
>> ff 45 31 ff 4c 87 7b 28 4d 85 ff 74 d6 44
>> 2022-12-22T14:09:51.419429+08:00 [localhost] kernel: RSP:
>> 0018:ffffc90000b13df0 EFLAGS: 00010246
>> 2022-12-22T14:09:51.419430+08:00 [localhost] kernel: RAX:
>> ffff888101caccc0 RBX: 0000000000000000 RCX: 0000000000000000
>> 2022-12-22T14:09:51.419430+08:00 [localhost] kernel: RDX:
>> 0000000010000088 RSI: 000000000005a844 RDI: ffff8881027bf000
>> 2022-12-22T14:09:51.419431+08:00 [localhost] kernel: RBP:
>> ffff8881027bf000 R08: 0000000000000000 R09: ffff8881027bf2a8
>> 2022-12-22T14:09:51.419431+08:00 [localhost] kernel: R10:
>> 0000000000000000 R11: 0000000000000000 R12: 0000000000000024
>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: R13:
>> 000000000005a844 R14: 000000000005a844 R15: 0000000000000000
>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: FS:
>> 00007ff03fdf0b80(0000) GS:ffff88883f380000(0000)
>> knlGS:0000000000000000
>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: CS: 0010 DS:
>> 0000 ES: 0000 CR0: 0000000080050033
>> 2022-12-22T14:09:51.419433+08:00 [localhost] kernel: CR2:
>> 0000000000000024 CR3: 000000013d64e006 CR4: 0000000000770ee0
>> 2022-12-22T14:09:51.419433+08:00 [localhost] kernel: PKRU: 55555554
>> 2022-12-22T14:09:51.419434+08:00 [localhost] kernel: Call Trace:
>> 2022-12-22T14:09:51.419434+08:00 [localhost] kernel: <TASK>
>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>> preempt_count_add+0x63/0x90
>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>> preempt_count_add+0x63/0x90
>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>> preempt_count_add+0x63/0x90
>> 2022-12-22T14:09:51.419436+08:00 [localhost] kernel:
>> f2fs_do_sync_file+0x489/0x650
>> 2022-12-22T14:09:51.419436+08:00 [localhost] kernel: __x64_sys_fsync+0x2f/0x60
>> 2022-12-22T14:09:51.419437+08:00 [localhost] kernel: do_syscall_64+0x35/0x80
>> 2022-12-22T14:09:51.419437+08:00 [localhost] kernel:
>> entry_SYSCALL_64_after_hwframe+0x46/0xb0
>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: RIP: 0033:0x7ff03feef20b
>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: Code: 3d 00 f0 ff
>> ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 a3 a2 f8
>> ff 8b 7c 24 0c 41 89 c0 b8 4a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35
>> 44 89 c7 89 44 24 0c e8 01 a3 f8 ff 8b 44
>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: RSP:
>> 002b:00007ffe6ecca530 EFLAGS: 00000293 ORIG_RAX: 000000000000004a
>> 2022-12-22T14:09:51.419439+08:00 [localhost] kernel: RAX:
>> ffffffffffffffda RBX: 0000000000000001 RCX: 00007ff03feef20b
>> 2022-12-22T14:09:51.419439+08:00 [localhost] kernel: RDX:
>> 0000000000000002 RSI: 0000000000000002 RDI: 0000000000000003
>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: RBP:
>> 0000000000002000 R08: 0000000000000000 R09: 00000000024bcfb0
>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: R10:
>> fffffffffffff4bf R11: 0000000000000293 R12: 00000000000006b7
>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: R13:
>> 000000000000003d R14: 0000000000000000 R15: 00000000024a1680
>> 2022-12-22T14:09:51.419441+08:00 [localhost] kernel: </TASK>
>> 2022-12-22T14:09:51.419441+08:00 [localhost] kernel: Modules linked
>> in: [last unloaded: ecc]
>> 2022-12-22T14:09:51.419442+08:00 [localhost] kernel: CR2: 0000000000000024
>> 2022-12-22T14:09:51.419442+08:00 [localhost] kernel: ---[ end trace
>> 0000000000000000 ]---
>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: RIP:
>> 0010:f2fs_issue_flush+0x10e/0x180
>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: Code: ba 01 00 00
>> 00 be 03 00 00 00 e8 ad e8 d5 ff 48 83 3b 00 74 1e 48 89 e7 e8 7f c1
>> 84 00 f0 ff 4b 24 8b 44 24 2c e9 66 ff ff ff <f0> ff 43 24 e9 4a ff ff
>> ff 45 31 ff 4c 87 7b 28 4d 85 ff 74 d6 44
>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: RSP:
>> 0018:ffffc90003903df0 EFLAGS: 00010246
>> 2022-12-22T14:09:51.419444+08:00 [localhost] kernel: RAX:
>> ffff888100106d80 RBX: 0000000000000000 RCX: 0000000000000000
>> 2022-12-22T14:09:51.419444+08:00 [localhost] kernel: RDX:
>> 0000000010000088 RSI: 0000000000b0e2ba RDI: ffff888116227000
>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: RBP:
>> ffff888116227000 R08: 0000000000000000 R09: ffff8881162272a8
>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: R10:
>> 0000000000000000 R11: 0000000000000000 R12: 0000000000000024
>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: R13:
>> 0000000000b0e2ba R14: 0000000000b0e2ba R15: 0000000000000000
>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: FS:
>> 00007ff03fdf0b80(0000) GS:ffff88883f380000(0000)
>> knlGS:0000000000000000
>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: CS: 0010 DS:
>> 0000 ES: 0000 CR0: 0000000080050033
>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: CR2:
>> 0000000000000024 CR3: 000000013d64e006 CR4: 0000000000770ee0
>> 2022-12-22T14:09:51.419447+08:00 [localhost] kernel: PKRU: 55555554
>
> Thanks for the report! I'm adding this to regzbot:
>
> #regzbot ^introduced v6.1.1..v6.2
> #regzbot title f2fs: kernel NULL pointer dereference when writing file
>
Oops, I mean:
#regzbot introduced v6.1.1..72a85e2b0a1e1e
Also, Cc'ed other F2FS maintainers and relevant lists.
Thanks.
--
An old man doll... just what I always wanted! - Clara
_______________________________________________
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] Fwd: f2fs write error Linux v6.2
2022-12-30 4:04 ` [f2fs-dev] Fwd: " Jeff Chua
@ 2022-12-30 5:56 ` Thorsten Leemhuis
2022-12-30 6:39 ` Eric Biggers
2023-02-17 12:48 ` Linux regression tracking (Thorsten Leemhuis)
0 siblings, 2 replies; 10+ messages in thread
From: Thorsten Leemhuis @ 2022-12-30 5:56 UTC (permalink / raw)
To: Jeff Chua, lkml, Linus Torvalds, Bagas Sanjaya, Jaegeuk Kim,
Chao Yu, F2FS Development, Linux Regressions
On 30.12.22 05:04, Jeff Chua wrote:
> On 12/24/22 19:43, Bagas Sanjaya wrote:
>> On Sat, Dec 24, 2022 at 01:48:55PM +0800, Jeff Chua wrote:
>>> Got the following error in latest linux-6.2-git with just vim (:w
>>> file1). No problem with linux-6.1.1
>
> What happened to the f2fs developers? No response from anyone yet.
Well, that indeed is unfortunate and ideally shouldn't happen, but the
simple reality is: that can happen this time of the year due to this
thing called "festive season".
> Am
> I the only one facing this? Linux-6.2 is unusable until this is fixed.
> What can I do to help?
The usual: bisect the issue, as then (a) we know exactly which developer
caused it, (b) which subsystem/maintainer is responsible (issues in a fs
might be caused by the VFS, block layer, mm, ...), and (c) might be able
to quickly revert that culprit, even if the people normally responsible
are MIA for some reason.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
>>> 2022-12-22T14:09:51.419409+08:00 [localhost] kernel: BUG: kernel NULL
>>> pointer dereference, address: 0000000000000024
>>> 2022-12-22T14:09:51.419422+08:00 [localhost] kernel: #PF: supervisor
>>> write access in kernel mode
>>> 2022-12-22T14:09:51.419423+08:00 [localhost] kernel: #PF:
>>> error_code(0x0002) - not-present page
>>> 2022-12-22T14:09:51.419424+08:00 [localhost] kernel: PGD 147b63067 P4D
>>> 147b63067 PUD 177d5c067 PMD 0
>>> 2022-12-22T14:09:51.419424+08:00 [localhost] kernel: Oops: 0002 [#7] PREEMPT SMP
>>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: CPU: 6 PID: 22891
>>> Comm: vi Tainted: G UD 6.1.0 #11
>>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: Hardware name:
>>> LENOVO 21CCS1GL00/21CCS1GL00, BIOS N3AET69W (1.34 ) 12/05/2022
>>> 2022-12-22T14:09:51.419428+08:00 [localhost] kernel: RIP:
>>> 0010:f2fs_issue_flush+0x10e/0x180
>>> 2022-12-22T14:09:51.419429+08:00 [localhost] kernel: Code: ba 01 00 00
>>> 00 be 03 00 00 00 e8 ad e8 d5 ff 48 83 3b 00 74 1e 48 89 e7 e8 7f c1
>>> 84 00 f0 ff 4b 24 8b 44 24 2c e9 66 ff ff ff <f0> ff 43 24 e9 4a ff ff
>>> ff 45 31 ff 4c 87 7b 28 4d 85 ff 74 d6 44
>>> 2022-12-22T14:09:51.419429+08:00 [localhost] kernel: RSP:
>>> 0018:ffffc90000b13df0 EFLAGS: 00010246
>>> 2022-12-22T14:09:51.419430+08:00 [localhost] kernel: RAX:
>>> ffff888101caccc0 RBX: 0000000000000000 RCX: 0000000000000000
>>> 2022-12-22T14:09:51.419430+08:00 [localhost] kernel: RDX:
>>> 0000000010000088 RSI: 000000000005a844 RDI: ffff8881027bf000
>>> 2022-12-22T14:09:51.419431+08:00 [localhost] kernel: RBP:
>>> ffff8881027bf000 R08: 0000000000000000 R09: ffff8881027bf2a8
>>> 2022-12-22T14:09:51.419431+08:00 [localhost] kernel: R10:
>>> 0000000000000000 R11: 0000000000000000 R12: 0000000000000024
>>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: R13:
>>> 000000000005a844 R14: 000000000005a844 R15: 0000000000000000
>>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: FS:
>>> 00007ff03fdf0b80(0000) GS:ffff88883f380000(0000)
>>> knlGS:0000000000000000
>>> 2022-12-22T14:09:51.419432+08:00 [localhost] kernel: CS: 0010 DS:
>>> 0000 ES: 0000 CR0: 0000000080050033
>>> 2022-12-22T14:09:51.419433+08:00 [localhost] kernel: CR2:
>>> 0000000000000024 CR3: 000000013d64e006 CR4: 0000000000770ee0
>>> 2022-12-22T14:09:51.419433+08:00 [localhost] kernel: PKRU: 55555554
>>> 2022-12-22T14:09:51.419434+08:00 [localhost] kernel: Call Trace:
>>> 2022-12-22T14:09:51.419434+08:00 [localhost] kernel: <TASK>
>>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>>> preempt_count_add+0x63/0x90
>>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>>> preempt_count_add+0x63/0x90
>>> 2022-12-22T14:09:51.419435+08:00 [localhost] kernel: ?
>>> preempt_count_add+0x63/0x90
>>> 2022-12-22T14:09:51.419436+08:00 [localhost] kernel:
>>> f2fs_do_sync_file+0x489/0x650
>>> 2022-12-22T14:09:51.419436+08:00 [localhost] kernel: __x64_sys_fsync+0x2f/0x60
>>> 2022-12-22T14:09:51.419437+08:00 [localhost] kernel: do_syscall_64+0x35/0x80
>>> 2022-12-22T14:09:51.419437+08:00 [localhost] kernel:
>>> entry_SYSCALL_64_after_hwframe+0x46/0xb0
>>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: RIP: 0033:0x7ff03feef20b
>>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: Code: 3d 00 f0 ff
>>> ff 77 48 c3 0f 1f 80 00 00 00 00 48 83 ec 18 89 7c 24 0c e8 a3 a2 f8
>>> ff 8b 7c 24 0c 41 89 c0 b8 4a 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35
>>> 44 89 c7 89 44 24 0c e8 01 a3 f8 ff 8b 44
>>> 2022-12-22T14:09:51.419438+08:00 [localhost] kernel: RSP:
>>> 002b:00007ffe6ecca530 EFLAGS: 00000293 ORIG_RAX: 000000000000004a
>>> 2022-12-22T14:09:51.419439+08:00 [localhost] kernel: RAX:
>>> ffffffffffffffda RBX: 0000000000000001 RCX: 00007ff03feef20b
>>> 2022-12-22T14:09:51.419439+08:00 [localhost] kernel: RDX:
>>> 0000000000000002 RSI: 0000000000000002 RDI: 0000000000000003
>>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: RBP:
>>> 0000000000002000 R08: 0000000000000000 R09: 00000000024bcfb0
>>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: R10:
>>> fffffffffffff4bf R11: 0000000000000293 R12: 00000000000006b7
>>> 2022-12-22T14:09:51.419440+08:00 [localhost] kernel: R13:
>>> 000000000000003d R14: 0000000000000000 R15: 00000000024a1680
>>> 2022-12-22T14:09:51.419441+08:00 [localhost] kernel: </TASK>
>>> 2022-12-22T14:09:51.419441+08:00 [localhost] kernel: Modules linked
>>> in: [last unloaded: ecc]
>>> 2022-12-22T14:09:51.419442+08:00 [localhost] kernel: CR2: 0000000000000024
>>> 2022-12-22T14:09:51.419442+08:00 [localhost] kernel: ---[ end trace
>>> 0000000000000000 ]---
>>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: RIP:
>>> 0010:f2fs_issue_flush+0x10e/0x180
>>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: Code: ba 01 00 00
>>> 00 be 03 00 00 00 e8 ad e8 d5 ff 48 83 3b 00 74 1e 48 89 e7 e8 7f c1
>>> 84 00 f0 ff 4b 24 8b 44 24 2c e9 66 ff ff ff <f0> ff 43 24 e9 4a ff ff
>>> ff 45 31 ff 4c 87 7b 28 4d 85 ff 74 d6 44
>>> 2022-12-22T14:09:51.419443+08:00 [localhost] kernel: RSP:
>>> 0018:ffffc90003903df0 EFLAGS: 00010246
>>> 2022-12-22T14:09:51.419444+08:00 [localhost] kernel: RAX:
>>> ffff888100106d80 RBX: 0000000000000000 RCX: 0000000000000000
>>> 2022-12-22T14:09:51.419444+08:00 [localhost] kernel: RDX:
>>> 0000000010000088 RSI: 0000000000b0e2ba RDI: ffff888116227000
>>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: RBP:
>>> ffff888116227000 R08: 0000000000000000 R09: ffff8881162272a8
>>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: R10:
>>> 0000000000000000 R11: 0000000000000000 R12: 0000000000000024
>>> 2022-12-22T14:09:51.419445+08:00 [localhost] kernel: R13:
>>> 0000000000b0e2ba R14: 0000000000b0e2ba R15: 0000000000000000
>>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: FS:
>>> 00007ff03fdf0b80(0000) GS:ffff88883f380000(0000)
>>> knlGS:0000000000000000
>>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: CS: 0010 DS:
>>> 0000 ES: 0000 CR0: 0000000080050033
>>> 2022-12-22T14:09:51.419446+08:00 [localhost] kernel: CR2:
>>> 0000000000000024 CR3: 000000013d64e006 CR4: 0000000000770ee0
>>> 2022-12-22T14:09:51.419447+08:00 [localhost] kernel: PKRU: 55555554
>>
>> Thanks for the report! I'm adding this to regzbot:
>>
>> #regzbot ^introduced v6.1.1..v6.2
>> #regzbot title f2fs: kernel NULL pointer dereference when writing file
>>
>
> Oops, I mean:
>
> #regzbot introduced v6.1.1..72a85e2b0a1e1e
>
> Also, Cc'ed other F2FS maintainers and relevant lists.
>
> Thanks.
>
> --
> An old man doll... just what I always wanted! - Clara
>
>
_______________________________________________
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] Fwd: f2fs write error Linux v6.2
2022-12-30 5:56 ` Thorsten Leemhuis
@ 2022-12-30 6:39 ` Eric Biggers
2022-12-30 7:15 ` Yangtao Li via Linux-f2fs-devel
2022-12-31 2:51 ` Chao Yu
2023-02-17 12:48 ` Linux regression tracking (Thorsten Leemhuis)
1 sibling, 2 replies; 10+ messages in thread
From: Eric Biggers @ 2022-12-30 6:39 UTC (permalink / raw)
To: Thorsten Leemhuis
Cc: Linux Regressions, Jeff Chua, lkml, F2FS Development,
Bagas Sanjaya, Jaegeuk Kim, Linus Torvalds
On Fri, Dec 30, 2022 at 06:56:36AM +0100, Thorsten Leemhuis wrote:
> On 30.12.22 05:04, Jeff Chua wrote:
> > On 12/24/22 19:43, Bagas Sanjaya wrote:
> >> On Sat, Dec 24, 2022 at 01:48:55PM +0800, Jeff Chua wrote:
> >>> Got the following error in latest linux-6.2-git with just vim (:w
> >>> file1). No problem with linux-6.1.1
> >
> > What happened to the f2fs developers? No response from anyone yet.
>
> Well, that indeed is unfortunate and ideally shouldn't happen, but the
> simple reality is: that can happen this time of the year due to this
> thing called "festive season".
>
> > Am
> > I the only one facing this? Linux-6.2 is unusable until this is fixed.
> > What can I do to help?
>
> The usual: bisect the issue, as then (a) we know exactly which developer
> caused it, (b) which subsystem/maintainer is responsible (issues in a fs
> might be caused by the VFS, block layer, mm, ...), and (c) might be able
> to quickly revert that culprit, even if the people normally responsible
> are MIA for some reason.
>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
>
FWIW, I've tested f2fs on mainline in the last few days, and I haven't seen
this. The following works fine, for example:
mkfs.f2fs -f /dev/vdb
mount /dev/vdb /mnt
vim
# write something, then ':w /mnt/file'
If you could provide the mkfs and mount options you are using, and any other
relevant details, that would be helpful. Bisection would also be very helpful,
as Thorsten mentioned.
- Eric
_______________________________________________
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] Fwd: f2fs write error Linux v6.2
2022-12-30 6:39 ` Eric Biggers
@ 2022-12-30 7:15 ` Yangtao Li via Linux-f2fs-devel
2022-12-31 12:01 ` Jeff Chua
2022-12-31 2:51 ` Chao Yu
1 sibling, 1 reply; 10+ messages in thread
From: Yangtao Li via Linux-f2fs-devel @ 2022-12-30 7:15 UTC (permalink / raw)
To: ebiggers
Cc: regressions, jeff.chua.linux, linux-kernel, linux-f2fs-devel,
regressions, bagasdotme, jaegeuk, torvalds
> What happened to the f2fs developers? No response from anyone yet. Am
> I the only one facing this? Linux-6.2 is unusable until this is fixed.
> What can I do to help?
It's been a long time since I saw Kim and Chao respond to messages. I think
it may be because of the holiday in the US，and China loosened restrictions
on COVID-19 (lots of people got sick, I just recovered today).
BTW, the log you uploaded corresponds to which kernel git is, and which
commit it corresponds to.
Thx,
Yangtao
_______________________________________________
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] Fwd: f2fs write error Linux v6.2
2022-12-30 6:39 ` Eric Biggers
2022-12-30 7:15 ` Yangtao Li via Linux-f2fs-devel
@ 2022-12-31 2:51 ` Chao Yu
2022-12-31 11:57 ` Jeff Chua
1 sibling, 1 reply; 10+ messages in thread
From: Chao Yu @ 2022-12-31 2:51 UTC (permalink / raw)
To: Jeff Chua, Thorsten Leemhuis, Eric Biggers
Cc: Linux Regressions, lkml, F2FS Development, Bagas Sanjaya,
Jaegeuk Kim, Linus Torvalds
Hi Jeff,
On 2022/12/30 14:39, Eric Biggers wrote:
> If you could provide the mkfs and mount options you are using, and any other
> relevant details, that would be helpful. Bisection would also be very helpful,
> as Thorsten mentioned.
Other than that, I found some cases which can cause similar issue, so I figure
out a patch for possible fixing, if you can have a try with it to check whether
it can fix your issue, that would be helpful as well.
https://lore.kernel.org/linux-f2fs-devel/20221230154332.5082-1-chao@kernel.org/T/#u
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] Fwd: f2fs write error Linux v6.2
2022-12-31 2:51 ` Chao Yu
@ 2022-12-31 11:57 ` Jeff Chua
2022-12-31 12:41 ` Jeff Chua
0 siblings, 1 reply; 10+ messages in thread
From: Jeff Chua @ 2022-12-31 11:57 UTC (permalink / raw)
To: Chao Yu
Cc: Linux Regressions, lkml, F2FS Development, Eric Biggers,
Thorsten Leemhuis, Bagas Sanjaya, Jaegeuk Kim, Linus Torvalds
On Sat, Dec 31, 2022 at 10:51 AM Chao Yu <chao@kernel.org> wrote:
>
> Hi Jeff,
>
> On 2022/12/30 14:39, Eric Biggers wrote:
> > If you could provide the mkfs and mount options you are using, and any other
> > relevant details, that would be helpful. Bisection would also be very helpful,
> > as Thorsten mentioned.
I was just preparing my environment so I could hit the same issue
before I go for the bisect, so I don't need to reboot every time. Got
to a point where I could just qemu kvm + initrd ramdisk with / (f2fs)
and I could hit the problem almost every 8/10 runs just by doing
"mount -o remount /" and the system would freeze. That's good. I've a
good test case! ... and then I see Chao Yu's patch ...
> Other than that, I found some cases which can cause similar issue, so I figure
> out a patch for possible fixing, if you can have a try with it to check whether
> it can fix your issue, that would be helpful as well.
>
> https://lore.kernel.org/linux-f2fs-devel/20221230154332.5082-1-chao@kernel.org/T/#u
Ok, the patch seems to fix the problem. I'll run my qemu kvm
environment a few more times before I switch the real system. Because
it's not a that I could cause a real "mount -o remount /" freeze or
"vi /etc/passwd" fault all the time,
Will feedback soon. This would a very nice year end celebration so I
could move to 6.2.0-rc1.
Thank you!
Jeff
_______________________________________________
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] Fwd: f2fs write error Linux v6.2
2022-12-30 7:15 ` Yangtao Li via Linux-f2fs-devel
@ 2022-12-31 12:01 ` Jeff Chua
0 siblings, 0 replies; 10+ messages in thread
From: Jeff Chua @ 2022-12-31 12:01 UTC (permalink / raw)
To: Yangtao Li
Cc: regressions, linux-kernel, linux-f2fs-devel, ebiggers,
regressions, bagasdotme, jaegeuk, torvalds
On Fri, Dec 30, 2022 at 3:16 PM Yangtao Li <frank.li@vivo.com> wrote:
>
> > What happened to the f2fs developers? No response from anyone yet. Am
> > I the only one facing this? Linux-6.2 is unusable until this is fixed.
> > What can I do to help?
>
> It's been a long time since I saw Kim and Chao respond to messages. I think
> it may be because of the holiday in the US，and China loosened restrictions
> on COVID-19 (lots of people got sick, I just recovered today).
>
> BTW, the log you uploaded corresponds to which kernel git is, and which
> commit it corresponds to.
Using the latest git pull ...
commit c8451c141e07a8d05693f6c8d0e418fbb4b68bb7 (HEAD -> master,
origin/master, origin/HEAD)
Merge: 262eef26e350 0948a9ef1d59
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date: Fri Dec 30 10:47:25 2022 -0800
I just applied Chao Yu's patch and it seems to hold ..
Thank you! Happy New Year!
Jeff
_______________________________________________
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] Fwd: f2fs write error Linux v6.2
2022-12-31 11:57 ` Jeff Chua
@ 2022-12-31 12:41 ` Jeff Chua
0 siblings, 0 replies; 10+ messages in thread
From: Jeff Chua @ 2022-12-31 12:41 UTC (permalink / raw)
To: Chao Yu, Yangtao Li
Cc: Linux Regressions, lkml, F2FS Development, Eric Biggers,
Thorsten Leemhuis, Bagas Sanjaya, Jaegeuk Kim, Linus Torvalds
On Sat, Dec 31, 2022 at 7:57 PM Jeff Chua <jeff.chua.linux@gmail.com> wrote:
>
> On Sat, Dec 31, 2022 at 10:51 AM Chao Yu <chao@kernel.org> wrote:
> >
> > Hi Jeff,
> >
> > On 2022/12/30 14:39, Eric Biggers wrote:
> > > If you could provide the mkfs and mount options you are using, and any other
> > > relevant details, that would be helpful. Bisection would also be very helpful,
> > > as Thorsten mentioned.
>
> I was just preparing my environment so I could hit the same issue
> before I go for the bisect, so I don't need to reboot every time. Got
> to a point where I could just qemu kvm + initrd ramdisk with / (f2fs)
> and I could hit the problem almost every 8/10 runs just by doing
> "mount -o remount /" and the system would freeze. That's good. I've a
> good test case! ... and then I see Chao Yu's patch ...
>
> > Other than that, I found some cases which can cause similar issue, so I figure
> > out a patch for possible fixing, if you can have a try with it to check whether
> > it can fix your issue, that would be helpful as well.
> >
> > https://lore.kernel.org/linux-f2fs-devel/20221230154332.5082-1-chao@kernel.org/T/#u
>
> Ok, the patch seems to fix the problem. I'll run my qemu kvm
> environment a few more times before I switch the real system. Because
> it's not a that I could cause a real "mount -o remount /" freeze or
> "vi /etc/passwd" fault all the time,
>
> Will feedback soon. This would a very nice year end celebration so I
> could move to 6.2.0-rc1.
Ok, no more freeze, no more errors! All good. I'm finally on the
latest linux-6.2.0-rc1 with the patch.
Happy new year!
My best,
Jeff
_______________________________________________
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] Fwd: f2fs write error Linux v6.2
2022-12-30 5:56 ` Thorsten Leemhuis
2022-12-30 6:39 ` Eric Biggers
@ 2023-02-17 12:48 ` Linux regression tracking (Thorsten Leemhuis)
1 sibling, 0 replies; 10+ messages in thread
From: Linux regression tracking (Thorsten Leemhuis) @ 2023-02-17 12:48 UTC (permalink / raw)
To: Jeff Chua, lkml, Linus Torvalds, Bagas Sanjaya, Jaegeuk Kim,
Chao Yu, F2FS Development, Linux Regressions
[TLDR: This mail in primarily relevant for Linux regression tracking. A
change or fix related to the regression discussed in this thread was
posted or applied, but it did not use a Link: tag to point to the
report, as Linus and the documentation call for. Things happen, no
worries -- but now the regression tracking bot needs to be told manually
about the fix. See link in footer if these mails annoy you.]
On 30.12.22 06:56, Thorsten Leemhuis wrote:
> On 30.12.22 05:04, Jeff Chua wrote:
>> On 12/24/22 19:43, Bagas Sanjaya wrote:
>>> On Sat, Dec 24, 2022 at 01:48:55PM +0800, Jeff Chua wrote:
>>>> Got the following error in latest linux-6.2-git with just vim (:w
>>>> file1). No problem with linux-6.1.1
>>
>> What happened to the f2fs developers? No response from anyone yet.
>
> Well, that indeed is unfortunate and ideally shouldn't happen, but the
> simple reality is: that can happen this time of the year due to this
> thing called "festive season".
> [...]
#regzbot fix: b3d83066cbebc76dbac8a5fca931f64b4c6fff34
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
_______________________________________________
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:[~2023-02-17 13:20 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <CAAJw_Ztzyh-GNTJYpXbA0CeJv2Rz=fLZKE6_Q=7JMmM+s9yHXQ@mail.gmail.com>
[not found] ` <CAAJw_Ztb0mJVkHtBhryf=9g8CA0fZZRa8HVio8GCGUSLOvqa7A@mail.gmail.com>
[not found] ` <Y6bz4wOC0nwu2yGU@debian.me>
2022-12-24 14:00 ` [f2fs-dev] f2fs write error Linux v6.2 Bagas Sanjaya
2022-12-30 4:04 ` [f2fs-dev] Fwd: " Jeff Chua
2022-12-30 5:56 ` Thorsten Leemhuis
2022-12-30 6:39 ` Eric Biggers
2022-12-30 7:15 ` Yangtao Li via Linux-f2fs-devel
2022-12-31 12:01 ` Jeff Chua
2022-12-31 2:51 ` Chao Yu
2022-12-31 11:57 ` Jeff Chua
2022-12-31 12:41 ` Jeff Chua
2023-02-17 12:48 ` Linux regression tracking (Thorsten Leemhuis)
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).