On 3/3/25 16:48, Matthew Wilcox wrote: > You need to turn on the debugging options Vlastimil mentioned and try to > figure out what nvme is doing wrong. Agree, looks like some error path going wrong? Since there seems to be actual non-large kmalloc usage involved, another debug parameter that could help: CONFIG_SLUB_DEBUG=y, and boot with "slab_debug=FZPU,kmalloc-*"
