Page MenuHomeFreeBSD

bhyve: Clear lid to 0 for internal device errors for NVMe AENs.
ClosedPublic

Authored by jhb on Nov 23 2022, 11:16 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sun, Nov 10, 6:58 PM
Unknown Object (File)
Sat, Oct 19, 5:56 AM
Unknown Object (File)
Oct 8 2024, 6:11 AM
Unknown Object (File)
Oct 4 2024, 4:10 AM
Unknown Object (File)
Oct 3 2024, 11:25 AM
Unknown Object (File)
Oct 1 2024, 11:06 AM
Unknown Object (File)
Sep 27 2024, 4:54 AM
Unknown Object (File)
Sep 24 2024, 4:04 AM

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jhb requested review of this revision.Nov 23 2022, 11:16 PM
This revision is now accepted and ready to land.Nov 24 2022, 6:32 AM

These changes are good but not really necessary from a functionality point of view. In both cases, the emulation is returning an error, making the LID undefined from the guest's perspective. But I'm all for good hygiene.

+1 on chuck's results. This can be anything.... but unassigned variables are allowed to have any behavior when accessing them now (well, always, but usually it was just some random value)... So I'm good with the change. It might be simpler to assign lid=0 before the case statement, though.

I think the real issue here is avoiding leaking host hypervisor stack memory to a guest, not if NVMe clients care about the value of lid for these specific cases.