#15144 closed bug (fixed)
nvme: received completion for unknown cmd
| Reported by: | jessicah | Owned by: | waddlesplash |
|---|---|---|---|
| Priority: | normal | Milestone: | R1/beta2 |
| Component: | Drivers/Disk/NVMe | Version: | R1/Development |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Attachments (1)
Change History (8)
by , 5 years ago
| Attachment: | IMG_20190709_154657.jpg added |
|---|
comment:1 by , 5 years ago
Maybe I have a corrupted partition, I haven't checked yet. Happened immediately after executing git log.
comment:2 by , 5 years ago
This is actually coming from libnvme. Disk corruption is irrelevant here; this is actually the drive itself sending something to us we do not expect. So that's pretty bad.
comment:3 by , 5 years ago
Diver reported in #15123 that there are often memory-related KDLs when nvme_disk is used. Perhaps that's related here -- this is really a use-after-free by libnvme, and our KDEBUG kernel overwrite the first few bytes of the allocated header.
comment:4 by , 5 years ago
This is probably resolved in hrev53997, but disk corruption still remains, I haven't solved that yet.
comment:5 by , 5 years ago
Actually the "corruption" may have just been on the underlying disk and compounded by some BFS driver issues when corruption is present. See comment in #15123; I'd wait to retest until Diver confirms that is gone however.
comment:6 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
As far as I can tell, these KDLs are fixed.
comment:7 by , 5 years ago
| Milestone: | Unscheduled → R1/beta2 |
|---|
Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone
KDL