UEFI getnextvariablename get EFI_INVALID_PARAMETER instead of EFI_BUFFER_TOO_SMALL

Bug #1593597 reported by Ivan Hu
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Firmware Test Suite
Fix Released
Low
Ivan Hu

Bug Description

Some firmwares (mostly on AMI Bios), the implementation limitation was seen that the VariableNameSize of the GetNextVariableName should lager or equal to 2. They believe that it should at least have a Null-terminated(2 bytes) for the name buffer.

So test getnextvariablename with VariableNameSize 0 and 1 will get the EFI_INVALID_PARAMETER, not expected EFI_BUFFER_TOO_SMALL.

For the fwts getnextvariablename buffer too small test(getnextvariable_test4),
1. add the VariableNameSize 2 for the test, if VariableNameSize 2 without returning EFI_BUFFER_TOO_SMALL, then test fail.
2. if VariableNameSize is 0 or 1, allow the extra return EFI_INVALID_PARAMETER.

Ivan Hu (ivan.hu)
Changed in fwts:
assignee: nobody → Ivan Hu (ivan.hu)
status: New → In Progress
importance: Undecided → Low
Revision history for this message
Ivan Hu (ivan.hu) wrote :

Patch had release on fwts V16.06.00

Changed in fwts:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.