Is there an existing issue for this?
Bug Type
What packages are impacted?
MdeModulePkg
Which targets are impacted by this bug?
DEBUG, RELEASE, NOOPT
Current Behavior
In the NvmExpressDriverBindingStart function, the Discover Nvme Namespaces function is called upon entering the start function, even if the driver is already started. I am confused whether this behavior is intentional or just a bug.
|
if (RemainingDevicePath == NULL) { |
|
// |
|
// Enumerate all NVME namespaces in the controller |
|
// |
|
Status = DiscoverAllNamespaces ( |
|
Private |
|
); |
|
} else if (!IsDevicePathEnd (RemainingDevicePath)) { |
|
// |
|
// Enumerate the specified NVME namespace |
|
// |
|
Status = Private->Passthru.GetNamespace ( |
|
&Private->Passthru, |
|
RemainingDevicePath, |
|
&NamespaceId |
|
); |
|
|
|
if (!EFI_ERROR (Status)) { |
|
Status = EnumerateNvmeDevNamespace ( |
|
Private, |
|
NamespaceId |
|
); |
|
} |
|
} |
Expected Behavior
Steps To Reproduce
Build Environment
- OS(s): N/A
- Tool Chain(s): Any
Version Information
Urgency
Low
Are you going to fix this?
I will fix it
Do you need maintainer feedback?
Maintainer feedback requested
Anything else?
No response
Is there an existing issue for this?
Bug Type
What packages are impacted?
MdeModulePkg
Which targets are impacted by this bug?
DEBUG, RELEASE, NOOPT
Current Behavior
In the NvmExpressDriverBindingStart function, the Discover Nvme Namespaces function is called upon entering the start function, even if the driver is already started. I am confused whether this behavior is intentional or just a bug.
edk2/MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpress.c
Lines 1149 to 1172 in d39a7ed
Expected Behavior
Steps To Reproduce
Build Environment
Version Information
Urgency
Low
Are you going to fix this?
I will fix it
Do you need maintainer feedback?
Maintainer feedback requested
Anything else?
No response