Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • L linux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Kirill Smelkov
  • linux
  • Repository
  • linux
  • tools
  • testing
  • selftests
  • exec
  • execveat.c
Find file BlameHistoryPermalink
  • Michael Ellerman's avatar
    selftests/exec: Check if the syscall exists and bail if not · 9a0b5745
    Michael Ellerman authored Feb 03, 2015
    
    
    On systems which don't implement sys_execveat(), this test produces a
    lot of output.
    
    Add a check at the beginning to see if the syscall is present, and if
    not just note one error and return.
    
    When we run on a system that doesn't implement the syscall we will get
    ENOSYS back from the kernel, so change the logic that handles
    __NR_execveat not being defined to also use ENOSYS rather than -ENOSYS.
    
    Signed-off-by: default avatarMichael Ellerman <mpe@ellerman.id.au>
    Acked-by: default avatarDavid Drysdale <drysdale@google.com>
    Signed-off-by: default avatarShuah Khan <shuahkh@osg.samsung.com>
    9a0b5745
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7