> But mostly, I would argue that this is a bug in the Intel NVMe driver.
You're commenting in the wrong bug. This bug is already being addressed. Please go over to bug 1653797
> But mostly, I would argue that this is a bug in the Intel NVMe driver.
You're commenting in the wrong bug. This bug is already being addressed. Please go over to bug 1653797