Skip to content

Comments

Use seccomp_unotify to catch syscalls that violate filterss#11375

Open
copybara-service[bot] wants to merge 1 commit intomasterfrom
test/cl713139953
Open

Use seccomp_unotify to catch syscalls that violate filterss#11375
copybara-service[bot] wants to merge 1 commit intomasterfrom
test/cl713139953

Conversation

@copybara-service
Copy link

@copybara-service copybara-service bot commented Jan 17, 2025

Use seccomp_unotify to catch syscalls that violate filterss

The main benefit of seccomp_unotify is an ability to resume the trapped syscall.
We have seen a case when a blocked syscall was in the msan internals that
prevented the Go runtime from reaching the SIGSYS handler and producing a panic
report.

Another benefit of this approach is an ability to run a target application and
find out all syscalls that have to be handled.

@copybara-service copybara-service bot added the exported Issue was exported automatically label Jan 17, 2025
@copybara-service copybara-service bot force-pushed the test/cl713139953 branch 2 times, most recently from 03fff58 to d8d0c7d Compare January 17, 2025 23:34
The main benefit of seccomp_unotify is an ability to resume the trapped syscall.
We have seen a case when a blocked syscall was in the msan internals that
prevented the Go runtime from reaching the SIGSYS handler and producing a panic
report.

Another benefit of this approach is an ability to run a target application and
find out all syscalls that have to be handled.

PiperOrigin-RevId: 713139953
@zhimin-z
Copy link

A friendly reminder that this PR had no activity for 120 days.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

exported Issue was exported automatically

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants