Re: [PATCH -next] ext4: fix bug_on in start_this_handle during umount filesystem
From: Theodore Ts'o
Date: Sun Apr 03 2022 - 10:08:46 EST
On Tue, 22 Mar 2022 09:24:19 +0800, Ye Bin wrote:
> We got issue as follows:
> ------------[ cut here ]------------
> kernel BUG at fs/jbd2/transaction.c:389!
> invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
> CPU: 9 PID: 131 Comm: kworker/9:1 Not tainted 5.17.0-862.14.0.6.x86_64-00001-g23f87daf7d74-dirty #197
> Workqueue: events flush_stashed_error_work
> RIP: 0010:start_this_handle+0x41c/0x1160
> RSP: 0018:ffff888106b47c20 EFLAGS: 00010202
> RAX: ffffed10251b8400 RBX: ffff888128dc204c RCX: ffffffffb52972ac
> RDX: 0000000000000200 RSI: 0000000000000004 RDI: ffff888128dc2050
> RBP: 0000000000000039 R08: 0000000000000001 R09: ffffed10251b840a
> R10: ffff888128dc204f R11: ffffed10251b8409 R12: ffff888116d78000
> R13: 0000000000000000 R14: dffffc0000000000 R15: ffff888128dc2000
> FS: 0000000000000000(0000) GS:ffff88839d680000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000001620068 CR3: 0000000376c0e000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> <TASK>
> jbd2__journal_start+0x38a/0x790
> jbd2_journal_start+0x19/0x20
> flush_stashed_error_work+0x110/0x2b3
> process_one_work+0x688/0x1080
> worker_thread+0x8b/0xc50
> kthread+0x26f/0x310
> ret_from_fork+0x22/0x30
> </TASK>
> Modules linked in:
> ---[ end trace 0000000000000000 ]---
>
> [...]
Applied, thanks!
[1/1] ext4: fix bug_on in start_this_handle during umount filesystem
commit: 20164749617e56d584313ad775d6dd3b7da40dc1
Best regards,
--
Theodore Ts'o <tytso@xxxxxxx>