After a first look at the kernel bug trace, it seems that q->make_request_fn(q, bio) (block/blk-core.c:1064) became NULL.
The reason might be a race with a block device not yet properly initialized when some I/O requests were submitted (or a block device de- registered too early while some I/O was still in progress), but, considering it was triggered upon a mount, I would say the former scenario is more likely to be the case. I haven't noticed any potentially related fix in DM or in the core block layer. I'll keep investigating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860231 Title: 5.4.0-11 crash on cryptsetup open To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860231/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
