Skip to content

runsc: allow readv for direct TAP links - #14232

Open
tianyuzhou95 wants to merge 1 commit into
google:masterfrom
tianyuzhou95:albert/readv-seccomp
Open

runsc: allow readv for direct TAP links#14232
tianyuzhou95 wants to merge 1 commit into
google:masterfrom
tianyuzhou95:albert/readv-seccomp

Conversation

@tianyuzhou95

Copy link
Copy Markdown
Contributor

Allow the sentry to use readv when an fdbased endpoint receives a non-socket file descriptor such as a TAP or TUN device. The dispatcher already selects readv for these supported descriptors, but the common seccomp policy previously terminated the sentry on its first packet.

This keeps the seccomp policy aligned with the existing fdbased receive path used by direct TAP links.

Allow the sentry to use readv when an fdbased endpoint receives a
non-socket file descriptor such as a TAP or TUN device. The dispatcher
already selects readv for these supported descriptors, but the common
seccomp policy previously terminated the sentry on its first packet.

This keeps the seccomp policy aligned with the existing fdbased receive
path used by direct TAP links.

Signed-off-by: Tianyu Zhou <albert.zty@antgroup.com>
@tianyuzhou95

Copy link
Copy Markdown
Contributor Author

Friendly ping @konstantin-s-bogom @nybidari — when you have a chance, could you please take a look at this?
I was also wondering if there are any concerns with allowing readv() in the common seccomp allow list, or if you'd prefer a more narrowly scoped approach. Thanks!

@konstantin-s-bogom konstantin-s-bogom left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah it looks OK, we already allow readv and preadv2 so this shouldn't increase the exposed host surface area.

copybara-service Bot pushed a commit that referenced this pull request Aug 27, 2026
Allow the sentry to use readv when an fdbased endpoint receives a non-socket file descriptor such as a TAP or TUN device. The dispatcher already selects readv for these supported descriptors, but the common seccomp policy previously terminated the sentry on its first packet.

This keeps the seccomp policy aligned with the existing fdbased receive path used by direct TAP links.

FUTURE_COPYBARA_INTEGRATE_REVIEW=#14232 from tianyuzhou95:albert/readv-seccomp bb9b1dd
PiperOrigin-RevId: 971992510
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants