Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the note about adding MU_CHANGE comments #101

Merged
merged 5 commits into from
Oct 29, 2020

Conversation

corthon
Copy link
Member

@corthon corthon commented Oct 25, 2020

Extra dash changes are to pass updated markdownlint.

@corthon corthon requested a review from spbrogan October 27, 2020 21:05
@corthon corthon requested review from makubacki and out0xb2 October 28, 2020 16:44
EFI_STATUS
EFIAPI
SomeFunction (
VOID
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indentation looks like 8 spaces instead of 2. Was that intentional?

)
{
EFI_STATUS Status;
// MU_CHANGE [BEGIN] - Add new counters for Feature X
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the single line comment/tag still allowed? If so, it might help clarify by providing a single line example as well.

@corthon corthon merged commit c9119b9 into master Oct 29, 2020
@corthon
Copy link
Member Author

corthon commented Oct 29, 2020

Apologies! My browser didn't refresh to show that there were additional comments. Will address these in another PR.

julorenz117 pushed a commit to julorenz117/mu that referenced this pull request Aug 19, 2024
## Description

Our memory protection policy is now robust enough to ensure that
platforms have no read/write/execute pages before ExitBootServices. This
update adds a test to the DxePagingAuditApp to check the page table for
RWX pages and only exempt them if the region is part of a nonprotected
image or special region.

Users can still utilize the app to dump paging data to the EFI partition
by calling the application with the '-d' flag. By default, the app will
run the RWX test.

## Breaking change?

No

## How This Was Tested

Running the test on Q35

## Integration Instructions

The test will identify RWX regions. Platforms should identify these
regions to determine if they must be RWX. If they really must be RWX,
the platform can utilize the Memory Protection Special Region Protocol
to create a special region.
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.

3 participants