For the record, I personally ran into this specific issue with some
moderate use of a ZFS pool:

[Mon Jul  3 10:07:56 2023] RIP: 0010:__list_del_entry_valid+0x0/0x70
[Mon Jul  3 10:07:56 2023] Code: 39 c0 0f 85 89 cf 4b 00 48 39 d7 0f 84 69 cf 
4b 00 4c 39 c7 0f 84 60 cf 4b 00 b8 01 00 00 00 c3 cc cc cc cc 66 0f 1f 44 00 
00 <48> 8b 17 48
 8b 4f 08 48 85 d2 0f 84 8d cf 4b 00 48 85 c9 0f 84 e2                          
                                                                                
            
[Mon Jul  3 10:07:56 2023] RSP: 0018:ffffb517c1503d00 EFLAGS: 00010283
[Mon Jul  3 10:07:56 2023] RAX: 0000000080000000 RBX: ffff99a572c070d8 RCX: 
0000000000000000
[Mon Jul  3 10:07:56 2023] RDX: 0000000000000001 RSI: ffffffff88fa639d RDI: 
dead000000000100
[Mon Jul  3 10:07:56 2023] RBP: ffff999f44344800 R08: 0000000000000000 R09: 
0000000080200011
[Mon Jul  3 10:07:56 2023] R10: 000000000000000a R11: 0000000000000001 R12: 
ffff99a4c3b867b0
[Mon Jul  3 10:07:56 2023] R13: ffff99a572c071e0 R14: dead000000000100 R15: 
dead000000000100
[Mon Jul  3 10:07:56 2023] FS:  0000000000000000(0000) 
GS:ffff99ae80080000(0000) knlGS:0000000000000000
[Mon Jul  3 10:07:56 2023] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033    
                                                                                
            
[Mon Jul  3 10:07:56 2023] CR2: 000000c01ea77000 CR3: 00000001283c8005 CR4: 
00000000003706e0
[Mon Jul  3 10:07:56 2023] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 
0000000000000000
[Mon Jul  3 10:07:56 2023] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 
0000000000000400
[Mon Jul  3 10:07:56 2023] Call Trace:                                          
                                                                                
            
[Mon Jul  3 10:07:56 2023]  <TASK>
[Mon Jul  3 10:07:56 2023]  zil_lwb_flush_vdevs_done+0xfe/0x2c0 [zfs]
[Mon Jul  3 10:07:56 2023]  zio_done+0x2c2/0x10f0 [zfs]
[Mon Jul  3 10:07:56 2023]  zio_execute+0x80/0x120 [zfs]
[Mon Jul  3 10:07:56 2023]  taskq_thread+0x2ba/0x4e0 [spl]
[Mon Jul  3 10:07:56 2023]  ? wake_up_q+0x90/0x90
[Mon Jul  3 10:07:56 2023]  ? zio_ddt_child_write_done+0xd0/0xd0 [zfs]
[Mon Jul  3 10:07:56 2023]  ? taskq_thread_spawn+0x50/0x50 [spl]
[Mon Jul  3 10:07:56 2023]  kthread+0xe6/0x110
[Mon Jul  3 10:07:56 2023]  ? kthread_complete_and_exit+0x20/0x20
[Mon Jul  3 10:07:56 2023]  ret_from_fork+0x1f/0x30
[Mon Jul  3 10:07:56 2023]  </TASK>

The bug has been fixed since commit
4f583a827e3b40f3bdfba78db75e1fe1feff122c via
https://github.com/openzfs/zfs/commit/55b1842f92a24fe7192d129bca7b60882080d31a,
which is present in RC1.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2025661

Title:
  Update Mantic package to OpenZFS 2.2.0-RC1

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hello,

  OpenZFS 2.2.0-RC1 has been released a couple of days ago.
  Could you update the Mantic package to this version?

  I'm personally asking because I'm running into a bug which has been
  fixed since commit 4f583a827e3b40f3bdfba78db75e1fe1feff122c, which is
  the version currently packaged.

  Thanks a lot!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2025661/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to