Does linux allow any system call to be made from signal handlers?

by

According to section 2 signal manual:

See signal(7) for a list of the async-signal-safe functions that can
be safely called from inside a signal handler.

And section 7 signals manual lists the following functions and/or system calls along with a pretty clear description:

Async-signal-safe functions

   A signal handler function must be very careful, since processing elsewhere may
   be interrupted at some arbitrary point in the execution of the program.  POSIX
   has the concept of "safe function".  If a signal interrupts the execution of
   an unsafe function, and handler calls an unsafe function, then the behavior of
   the program is undefined.

   POSIX.1-2004 (also known as POSIX.1-2001 Technical Corrigendum 2) requires an
   implementation to guarantee that the following functions can be safely called
   inside a signal handler:

       _Exit()
       _exit()
       abort()
       accept()
       access()
       aio_error()
       aio_return()
       aio_suspend()
       alarm()
       bind()
       cfgetispeed()
       cfgetospeed()
       cfsetispeed()
       cfsetospeed()
       chdir()
       chmod()
       chown()
       clock_gettime()
       close()
       connect()
       creat()
       dup()
       dup2()
       execle()
       execve()
       fchmod()
       fchown()
       fcntl()
       fdatasync()
       fork()
       fpathconf()
       fstat()
       fsync()
       ftruncate()
       getegid()
       geteuid()
       getgid()
       getgroups()
       getpeername()
       getpgrp()
       getpid()
       getppid()
       getsockname()
       getsockopt()
       getuid()
       kill()
       link()
       listen()
       lseek()
       lstat()
       mkdir()
       mkfifo()
       open()
       pathconf()
       pause()
       pipe()
       poll()
       posix_trace_event()
       pselect()
       raise()
       read()
       readlink()
       recv()
       recvfrom()
       recvmsg()
       rename()
       rmdir()
       select()
       sem_post()
       send()
       sendmsg()
       sendto()
       setgid()
       setpgid()
       setsid()
       setsockopt()
       setuid()
       shutdown()
       sigaction()
       sigaddset()
       sigdelset()
       sigemptyset()
       sigfillset()
       sigismember()
       signal()
       sigpause()
       sigpending()
       sigprocmask()
       sigqueue()
       sigset()
       sigsuspend()
       sleep()
       sockatmark()
       socket()
       socketpair()
       stat()
       symlink()
       sysconf()
       tcdrain()
       tcflow()
       tcflush()
       tcgetattr()
       tcgetpgrp()
       tcsendbreak()
       tcsetattr()
       tcsetpgrp()
       time()
       timer_getoverrun()
       timer_gettime()
       timer_settime()
       times()
       umask()
       uname()
       unlink()
       utime()
       wait()
       waitpid()
       write()

   POSIX.1-2008 removes fpathconf(), pathconf(), and sysconf() from the above
   list, and adds the following functions:

       execl()
       execv()
       faccessat()
       fchmodat()
       fchownat()
       fexecve()
       fstatat()
       futimens()
       linkat()
       mkdirat()
       mkfifoat()
       mknod()
       mknodat()
       openat()
       readlinkat()
       renameat()
       symlinkat()
       unlinkat()
       utimensat()
       utimes()

I believe this information to be more reliable than something that we hear sometimes somewhere . So Linux does allow only some system calls but not all of them. So the answer to your question is simply — no.

More Related Contents:

  1. How to avoid using printf in a signal handler?
  2. How to capture Control+D signal?
  3. Segmentation fault handling
  4. Signal handling with multiple threads in Linux
  5. How does sig_atomic_t actually work?
  6. Which thread handles the signal?
  7. Signal queuing in C
  8. Checking if errno != EINTR: what does it mean?
  9. Linux: Why is sig_atomic_t typedef’ed to int?
  10. executing default signal handler
  11. What’s the correct answer about getservbyname?
  12. Creating child process in C linux [closed]
  13. Catch Ctrl-C in C
  14. Why is the .bss segment required?
  15. Why does stat fail using a name from readdir? [duplicate]
  16. Erase the current printed console line
  17. Best way to invoke gdb from inside program to print its stacktrace?
  18. How to include needed C library using gcc?
  19. Unexpected exec permission from mmap when assembly files included in the project
  20. Whole one core dedicated to single process
  21. Finding out what the GCC include path is [duplicate]
  22. Bind failed: Address already in use
  23. Why do I have to define LD_LIBRARY_PATH with an export every time I run my application?
  24. Is there a macro definition to check the Linux kernel version?
  25. Writing to a closed, local TCP socket not failing
  26. Write to .txt file?
  27. Do forked child processes use the same semaphore?
  28. What’s a good C decompiler? [closed]
  29. Problem usage memory in C
  30. What are trade offs for “busy wait” vs “sleep”?

Leave a Comment