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

[LibOS] Do not reuse chroot_unlink() in shm filesystem #1815

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dimakuv
Copy link
Contributor

@dimakuv dimakuv commented Mar 14, 2024

Description of the changes

It is a bad smell to reuse functions intended for another subsystem. Also, a future commit will modify chroot_unlink() such that shm FS won't be able to reuse it.

Extracted from #1812.

How to test this PR?

N/A.


This change is Reviewable

It is a bad smell to reuse functions intended for another subsystem.
Also, a future commit will modify `chroot_unlink()` such that `shm` FS
won't be able to reuse it.

Signed-off-by: Dmitrii Kuvaiskii <dmitrii.kuvaiskii@intel.com>
@dimakuv dimakuv marked this pull request as ready for review March 14, 2024 13:11
Copy link
Contributor Author

@dimakuv dimakuv left a comment

Choose a reason for hiding this comment

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

Reviewable status: 0 of 4 files reviewed, all discussions resolved, not enough approvals from maintainers (2 more required), not enough approvals from different teams (1 more required, approved so far: Intel)


libos/src/fs/chroot/encrypted.c line 281 at r1 (raw file):

/* NOTE: this function is different from generic `chroot_unlink` only to add PAL_OPTION_PASSTHROUGH.
 * Once that option is removed, we can safely go back to using `chroot_unlink`. */

In #1812, it will differ in other ways too, so I just decided to remove the commit here (even though it's a bit unrelated)

Copy link
Contributor

@kailun-qin kailun-qin left a comment

Choose a reason for hiding this comment

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

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: all files reviewed, all discussions resolved, not enough approvals from different teams (1 more required, approved so far: Intel)

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.

None yet

2 participants