-
Notifications
You must be signed in to change notification settings - Fork 166
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.
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
proc_self_status
fails on second invocation
#994
Comments
sunfishcode
added a commit
that referenced
this issue
Jan 16, 2024
Fix `proc_self_status()` to reset the directory cursor before iterating through the directory entries when searching for bind mounts. This fixes a failure when called more than once, due to the cursor being left at the end. Fixes #994.
sunfishcode
added a commit
that referenced
this issue
Jan 16, 2024
Fix `proc_self_status()` to reset the directory cursor before iterating through the directory entries when searching for bind mounts. This fixes a failure when called more than once, due to the cursor being left at the end. Fixes #994.
sunfishcode
added a commit
that referenced
this issue
Jan 16, 2024
Fix `proc_self_status()` to reset the directory cursor before iterating through the directory entries when searching for bind mounts. This fixes a failure when called more than once, due to the cursor being left at the end. Fixes #994.
This is now released in rustix 0.38.31. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When calling
proc_self_status
a twice, it errors the second time with errorreliably on both back-ends (testing on linux).
This seems to have regressed from
rustix
version0.38.14
to0.38.15
. Maybe related to #859?proc_self_maps
andproc_self_pagemap
are also affected butproc_self_fd
is not. Also cross-usage is affected (e.g. firstproc_self_maps
and thenproc_self_pagemap
).Example
And cross-usage:
Environment
rustix
versions: >= 0.38.15The text was updated successfully, but these errors were encountered: