Hello,

I can confirm the same regression on another physical Debian 12 Bookworm system.

System:
- Debian 12 Bookworm
- Kernel 6.1.192-1 (6.1.0-55-amd64)
- Previous kernel: 6.1.190-1 (6.1.0-54-amd64)
- 16 GB RAM
- NVMe SSD, ext4 filesystem
- Motherboard: B75

The system experienced repeated kernel Oops messages during filesystem 
writeback, eventually becoming unresponsive.

Here is the relevant dmesg output from the first occurrence:

```text
[  128.541622] BUG: kernel NULL pointer dereference, address: 0000000000000000
[  128.541630] #PF: supervisor read access in kernel mode
[  128.541632] #PF: error_code(0x0000) - not-present page
[  128.541634] PGD 0 P4D 0
[  128.541637] Oops: 0000 [#1] PREEMPT SMP NOPTI
[  128.541640] CPU: 1 PID: 37 Comm: kworker/u8:3 Not tainted 6.1.0-55-amd64 #1 
Debian 6.1.192-1
[  128.541643] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./B75, BIOS 4.6.5 09/29/2021
[  128.541646] Workqueue: writeback wb_workfn (flush-259:0)
[  128.541653] RIP: 0010:ext4_mb_load_buddy_gfp+0xbc/0x380 [ext4]
[  128.541685] Code: 89 44 24 08 f7 3c 24 48 63 d8 89 54 24 0c ba 01 00 00 00 
48 89 de e8 d3 fe 12 f0 49 89 c7 48 3d 00 f0 ff ff 0f 87 28 01 00 00 <48> 8b 00 
a8 04 0f 84 12 01 00 00 49 8b 07 a8 01 0f 85 07 01 00 00
[  128.541689] RSP: 0018:ffffd297c016b550 EFLAGS: 00010207
[  128.541692] RAX: 0000000000000000 RBX: 00000000000006c2 RCX: 0000000000000001
[  128.541694] RDX: 0000000000000002 RSI: ffff8bb1a1058ff8 RDI: ffff8bb180c96600
[  128.541696] RBP: ffff8bb1d14e8800 R08: ffff8bb1d14e8800 R09: 0000000000000000
[  128.541698] R10: 0000000000000001 R11: 0000000000000000 R12: ffffd297c016b5e8
[  128.541699] R13: 0000000000000c40 R14: ffff8bb1d124d050 R15: 0000000000000000
[  128.541702] FS:  0000000000000000(0000) GS:ffff8bb48f280000(0000) 
knlGS:0000000000000000
[  128.541705] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  128.541707] CR2: 0000000000000000 CR3: 00000003bc410004 CR4: 00000000001706e0
[  128.541709] Call Trace:
[  128.541712]  <TASK>
[  128.541715]  ext4_mb_regular_allocator+0x29e/0xce0 [ext4]
[  128.541740]  ext4_mb_new_blocks+0x820/0x1240 [ext4]
[  128.541763]  ? jbd2_journal_dirty_metadata+0x166/0x230 [jbd2]
[  128.541774]  ext4_new_meta_blocks+0xd0/0x120 [ext4]
[  128.541794]  ext4_ext_insert_extent+0x56f/0x13c0 [ext4]
[  128.541815]  ? ext4_find_extent+0x3d3/0x430 [ext4]
[  128.541835]  ext4_ext_map_blocks+0x76e/0x1990 [ext4]
[  128.541855]  ? release_pages+0x159/0x470
[  128.541859]  ? find_get_pages_range_tag+0x1a9/0x200
[  128.541864]  ? __pagevec_release+0x1b/0x60
[  128.541867]  ext4_map_blocks+0x1b6/0x5f0 [ext4]
[  128.541889]  ext4_writepages+0x88a/0x1190 [ext4]
[  128.541912]  ? pagevec_lookup_range_tag+0x24/0x30
[  128.541917]  ? update_load_avg+0x7e/0x780
[  128.541920]  ? select_task_rq_fair+0x159/0x1840
[  128.541923]  do_writepages+0xbd/0x1c0
[  128.541927]  ? __wb_calc_thresh+0x4b/0x140
[  128.541930]  __writeback_single_inode+0x3d/0x360
[  128.541934]  writeback_sb_inodes+0x1f5/0x4d0
[  128.541938]  __writeback_inodes_wb+0x4c/0xf0
[  128.541942]  wb_writeback+0x204/0x2f0
[  128.541946]  wb_workfn+0x2aa/0x4f0
[  128.541950]  process_one_work+0x1c4/0x380
[  128.541954]  worker_thread+0x4d/0x380
[  128.541956]  ? rescuer_thread+0x3a0/0x3a0
[  128.541959]  kthread+0xd7/0x100
[  128.541962]  ? kthread_complete_and_exit+0x20/0x20
[  128.541966]  ret_from_fork+0x1f/0x30
[  128.541971]  </TASK>
[  128.541972] Modules linked in: [omitted]
[  129.157450] RIP: 0010:ext4_mb_load_buddy_gfp+0xbc/0x380 [ext4]
[  129.157524] note: kworker/u8:3[37] exited with irqs disabled
[  129.157580] ------------[ cut here ]------------
[  129.157583] WARNING: CPU: 1 PID: 37 at kernel/exit.c:823 do_exit+0x904/0xb10
[  129.157589] Modules linked in: [omitted]
```

The same Oops occurred again after rebooting with kernel 6.1.0-55.

After booting into kernel 6.1.0-54-amd64, the system has remained stable.

This is another confirmation of the regression on physical hardware.

Best regards

Reply via email to