Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
X
xen
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Raptor Engineering Public Development
  • xen
  • Repository

Switch branch/tag
  • xen
  • README
Find file BlameHistoryPermalink
  • Marek Marczykowski-Górecki's avatar
    x86: Build check for embedded endbr64 instructions · 4d037425
    Marek Marczykowski-Górecki authored Nov 26, 2021
    An interesting corner case occurs when the byte sequence making up endbr64
    ends up on a non-instruction boundary.  Such embedded instructions mark legal
    indirect branch targets as far as the CPU is concerned, which aren't legal as
    far as the logic is concerned.
    
    When CET-IBT is active, check for embedded byte sequences.  Example failures
    look like:
    
      check-endbr.sh xen-syms Fail: Found 2 embedded endbr64 instructions
      0xffff82d040325677: test_endbr64 at /local/xen.git/xen/arch/x86/x86_64/entry.S:28
      0xffff82d040352da6: init_done at /local/xen.git/xen/arch/x86/setup.c:675
    Signed-off-by: default avatarMarek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
    Signed-off-by: default avatarAndrew Cooper <andrew.cooper3@citrix.com>
    Reviewed-by: default avatarJan Beulich <jbeulich@suse.com>
    4d037425
README 8.5 KB
EditWeb IDE

Replace README

Attach a file by drag & drop or click to upload


Cancel
A new branch will be created in your fork and a new merge request will be started.

Powered by Integricloud