Skip to content

EFI_Variable_Validation: improve OsTrialBootStatus write diagnostics#476

Open
smuppand wants to merge 1 commit into
qualcomm-linux:mainfrom
smuppand:logger
Open

EFI_Variable_Validation: improve OsTrialBootStatus write diagnostics#476
smuppand wants to merge 1 commit into
qualcomm-linux:mainfrom
smuppand:logger

Conversation

@smuppand
Copy link
Copy Markdown
Contributor

@smuppand smuppand commented Jun 3, 2026

Update EFI_Variable_Validation to keep OsTrialBootStatus as the mandatory EFI variable validation target while improving parsing and failure diagnostics.

The validation goal remains unchanged: verify EFI runtime/efivarfs support and validate write/read behavior for OsTrialBootStatus.

  • Keep OsTrialBootStatus as the mandatory write/read validation variable.

  • Fix efivar -l count parsing to avoid integer comparison errors such as:

    [: 00: integer expected
    

OsTrialBootStatus is the platform validation target for this test, so keep
the mandatory EFI variable write/read validation on that variable instead
of replacing it with a generic test-owned variable.

Fix the efivar -l count parsing to avoid multiline values causing integer
comparison errors. Also improve diagnostics around the OsTrialBootStatus
write path by logging the existing variable state, efivarfs mount state,
efivarfs attributes when available, and recent EFI/efivar kernel messages
when the write fails.

This keeps the test aligned with the intended platform validation goal
while making EFI variable write failures easier to debug in CI.

Signed-off-by: Srikanth Muppandam <smuppand@qti.qualcomm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant