pulseaudio thread blocks all signals, disabling syscallbuf
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.7k
- Forks
- 662
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 2
Description
It blocks all signals using sigfillset/sigprocmask. This causes us to disable syscallbuf for that thread.
This isn't a big deal, but we could probably work around this by having syscallbuf vsyscall_hook intercept sigprocmask/rt_sigprocmask and remove SIGSYS from the blocked signal set.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the syscallbuf vsyscall_hook entry point and inspect how sigprocmask and rt_sigprocmask are handled. Trace the PulseAudio thread path that disables syscallbuf, then verify that both calls remove SIGSYS from the blocked signal set without disrupting other signal handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, linux
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100