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

A call to unshare(CLONE_FS) from tracee may break the emulation of cwd. #42

Open
Tracked by #45
imlk0 opened this issue Jul 22, 2021 · 1 comment
Open
Tracked by #45

A call to unshare(CLONE_FS) from tracee may break the emulation of cwd. #42

imlk0 opened this issue Jul 22, 2021 · 1 comment
Labels
bug

Comments

@imlk0
Copy link
Collaborator

imlk0 commented Jul 22, 2021 •
edited by oxr463
Loading

According to the unshare(2) man page:

A call to unshare(CLONE_FS) will:

       CLONE_FS
              Reverse the effect of the clone(2) CLONE_FS flag.  Unshare
              filesystem attributes, so that the calling process no
              longer shares its root directory (chroot(2)), current
              directory (chdir(2)), or umask (umask(2)) attributes with
              any other process.

There is no handling of unshare() by proot-rs yet, so I have documented it here.
@imlk0 imlk0 added the bug label Jul 22, 2021
@imlk0 imlk0 added this to the v0.0.1 milestone Jul 22, 2021
@imlk0 imlk0 self-assigned this Jul 22, 2021
@imlk0 imlk0 mentioned this issue Jul 26, 2021
Merged
13 tasks
@oxr463 oxr463 removed this from the v0.0.1 milestone Aug 11, 2021
@oxr463
Copy link
Contributor

oxr463 commented Aug 11, 2021

Per our conversation on Gitter,

This doesn't seem to have much impact at the moment, if have extra time I'll try to fix it.

I've removed it from the milestone for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@imlk0 @oxr463