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

recognize zram as swap #447

Merged
merged 3 commits into from
Oct 20, 2022
Merged

recognize zram as swap #447

merged 3 commits into from
Oct 20, 2022

Conversation

chri2
Copy link

@chri2 chri2 commented Oct 19, 2022

Check if unencrypted swap is zram. If it is zram check whether a writeback to disk is configured.

Unencrypted zramswap not written to disk is accepted.

ToDo (as for other unencrypted swap): check if the writeback happens on an already encrypted disk/partition.

Check if unencrypted swap is zram. If it is zram check whether a writeback to
disk is configured.

Unencrypted zramswap not written to disk is accepted.

ToDo (as for other unencrypted swap): check if the writeback happens on an
already encrypted disk/partition.
Something went wrong when I tried to move my changes from my installation
into the git. Now the tests complete successfully.
@chri2
Copy link
Author

chri2 commented Oct 19, 2022

recognizes zramswap as swap that lives in ram only if it doesn't write back to disk

#445

tomb Outdated Show resolved Hide resolved
As explained to me here dyne#447 (comment)
it would be bad to change existing messages. Reverted to the already existing messages
and added new messages about zramswap.
@jaromil jaromil merged commit 8502bdc into dyne:master Oct 20, 2022
@jaromil
Copy link
Member

jaromil commented Oct 20, 2022

thanks for your contribution and be welcome among tomb developers! 🎉

@chri2 chri2 deleted the chri2 branch October 20, 2022 14:48
@chri2
Copy link
Author

chri2 commented Oct 21, 2022

🥳

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