Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • D Driver Model U-Boot Custodian Tree
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • U-BootU-Boot
  • Custodians
  • Driver Model U-Boot Custodian Tree
  • Repository
Switch branch/tag
  • u-boot-dm
  • arch
  • sandbox
  • cpu
  • os.c
Find file BlameHistoryPermalink
  • Heinrich Schuchardt's avatar
    sandbox: don't set SA_NODEFER in signal handler · fd25ca32
    Heinrich Schuchardt authored Jul 05, 2021 and Simon Glass's avatar Simon Glass committed Jul 21, 2021
    
    
    The sandbox can handle signals. Due to a damaged global data pointer
    additional exceptions in the signal handler may occur leading to an endless
    loop. In this case leave the handling of the secondary exception to the
    operating system.
    
    Signed-off-by: Heinrich Schuchardt's avatarHeinrich Schuchardt <xypron.glpk@gmx.de>
    Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
    fd25ca32

Imprint & Privacy Policy