Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

gVisor VDSO may span multiple maps entries #157

Open
amscanne opened this issue Mar 25, 2019 · 4 comments
Open

gVisor VDSO may span multiple maps entries #157

amscanne opened this issue Mar 25, 2019 · 4 comments
Labels
area: kernel Issue related to core kernel (task management, etc) exported Issue was exported automatically priority: p3 Low priority revived The Issue has been revived by the issue reviver. type: bug Something isn't working type: cleanup Refactorings and cleanups to improve the code

Comments

@amscanne
Copy link
Contributor

The VDSO mapped by the sentry has a writable segment, so we have more than one maps entry.

Linux always has a single VDSO entry.

We currently avoid advertising the VDSO in maps to avoid breaking userspace programs that expect a single VDSO entry.
@amscanne amscanne added type: bug Something isn't working type: cleanup Refactorings and cleanups to improve the code exported Issue was exported automatically priority: p3 Low priority labels Mar 25, 2019
@prattmic prattmic added the area: kernel Issue related to core kernel (task management, etc) label Apr 3, 2020
@prattmic prattmic removed their assignment Apr 3, 2020
@github-actions
Copy link

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

@github-actions github-actions bot added the stale-issue This issue has not been updated in 120 days. label Sep 15, 2023
@ayushr2 ayushr2 removed the stale-issue This issue has not been updated in 120 days. label Sep 15, 2023
@github-actions GitHub Actions
Copy link

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

@github-actions github-actions bot added the stale-issue This issue has not been updated in 120 days. label Jan 14, 2024
@github-actions GitHub Actions
Copy link

This issue has been closed due to lack of activity.

@github-actions github-actions bot reopened this Apr 15, 2024
@github-actions GitHub Actions
Copy link

There are TODOs still referencing this issue:

  1. pkg/sentry/loader/vdso.go:224: Don't advertise the VDSO, as

Search TODO

@github-actions github-actions bot added revived The Issue has been revived by the issue reviver. and removed auto-closed stale-issue This issue has not been updated in 120 days. labels Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area: kernel Issue related to core kernel (task management, etc) exported Issue was exported automatically priority: p3 Low priority revived The Issue has been revived by the issue reviver. type: bug Something isn't working type: cleanup Refactorings and cleanups to improve the code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@amscanne @prattmic @ayushr2