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.

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

LTP: Fixed unshare01 and unshare02 #64

Merged
merged 1 commit into from
Aug 12, 2020
Merged

Conversation

vamsikrishna935
Copy link

  • Patch Description:
    Test were failing because of no fork support.
    Modified the tests without using fork and done code cleanup.

Copy link
Collaborator

@hukoyu hukoyu left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

@davidchisnall davidchisnall left a comment

Choose a reason for hiding this comment

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

I don't understand this patch. Unshare's behaviour is intrinsically linked to multiple processes, so we should just disable this test.

@vamsikrishna935
Copy link
Author

I don't understand this patch. Unshare's behaviour is intrinsically linked to multiple processes, so we should just disable this test.

@davidchisnall can we implement this using threads ?
Manpage statement : unshare() allows a process (or thread) to disassociate parts of its
execution context that are currently being shared with other
processes (or threads).

@davidchisnall
Copy link

I’m not sure what man page you’re reading, but the one I have does not mention threads. That said, the design doc for unshare indicates it applies to threads created with clone. I have no idea whether this will work correctly until Vikas’ patch lands, but it looks as if it should be possible to enable this with threads.

Copy link

@davidchisnall davidchisnall left a comment

Choose a reason for hiding this comment

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

I think these changes are okay, the test itself is pretty useless: it tests that the syscall returns success, not that it actually does anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants