-
Notifications
You must be signed in to change notification settings - Fork 91
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
Verify that loading images with <4k section alignment either succeeds or fails gracefully (Bugzilla Bug 1860) #222
Comments
Comment 7851Date: 2019-05-29 06:43:55 +0000
We have seen issues in the field where platforms that enable NX attribute on the pe/coff header hang hard when presented. So it would be beneficial if we had a test that verified graceful failure (or success) of images with <4k section alignment. |
Comment 7916Date: 2019-06-03 14:50:12 +0000 Acknowledged. |
Comment 9818Date: 2019-09-25 19:04:53 +0000 Can you please point me to relevant section in the UEFI Specification which mandates section alignment restrictions so that additional test case can be added to existing image tests? |
Comment 9822Date: 2019-09-25 20:09:28 +0000 There is no explicit statement about the alignment. There is an implicit requirement that if you want to use EFI_MEMORY_XP attribute, you need to keep non-executable regions in separate pages from executable regions - for example ensuring the page containing the PE header does not also contain code. The request is for a test that ensures that if a platform enforces restrictions on alignment, then it fails gracefully when an image with smaller alignment is executed. Today we have platforms in the wild that hang hard if you execute a program with < 4k section alignment. |
Comment 15869Date: 2021-05-01 04:40:51 +0000 @leif: |
Comment 16231Date: 2021-06-01 07:54:34 +0000 Supreeth left ARM a while ago - re-assigning to Edhay for consideration. |
Comment 18839Date: 2022-04-19 10:51:08 +0000 @lief: Can your team provide a patch for this solution? |
This issue was created automatically with bugzilla2github
Bugzilla Bug 1860
Date: 2019-05-29T06:43:55+00:00
From: @leiflindholm
To: Edhay <<edhaya.chandran>>
CC: arvin.chen, benjamin.you, edhaya.chandran, eric.jin, gaojie, @leiflindholm, samer.el-haj-mahmoud, siyuan.fu, xypron.glpk
Last updated: 2022-04-19T10:51:08+00:00
The text was updated successfully, but these errors were encountered: