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
gpt-auto-generator: Use volatile-root by default and automatic logic as fallback #20578
Merged
yuwata
merged 1 commit into
systemd:main
from
klausenbusk:gpt-auto-generator-volatile-fs
Aug 31, 2021
Merged
gpt-auto-generator: Use volatile-root by default and automatic logic as fallback #20578
yuwata
merged 1 commit into
systemd:main
from
klausenbusk:gpt-auto-generator-volatile-fs
Aug 31, 2021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
poettering
reviewed
Aug 30, 2021
poettering
added
gpt-auto
reviewed/needs-rework 🔨
PR has been reviewed and needs another round of reworks
labels
Aug 30, 2021
Also, please update the man page of the generator to document the symlink. If this is now official API for other components too, then this must be documented. So far this was in internal interface only, thus had no docs. |
klausenbusk
force-pushed
the
gpt-auto-generator-volatile-fs
branch
from
August 30, 2021 10:59
f513b32
to
f5830dc
Compare
klausenbusk
changed the title
gpt-auto-generator: Also use volatile-root fallback when the originating device can't be found
gpt-auto-generator: Use volatile-root by default and automatic logic as fallback
Aug 30, 2021
I have shuffled the code around so |
poettering
reviewed
Aug 30, 2021
klausenbusk
force-pushed
the
gpt-auto-generator-volatile-fs
branch
from
August 30, 2021 11:46
f5830dc
to
f71c918
Compare
poettering
requested changes
Aug 30, 2021
…as fallback Previously volatile-root was only checked if "/" wasn't backed by a block device, but the block device isn't necessarily original root block device (ex: if the rootfs is copied to a ext4 fs backed by zram in the initramfs), so we always want volatile-root checked. So shuffle the code around so volatile-root is checked first and fallback to the automatic logic. Fix systemd#20557
klausenbusk
force-pushed
the
gpt-auto-generator-volatile-fs
branch
from
August 30, 2021 12:01
f71c918
to
f8e7e84
Compare
lgtm |
poettering
added
good-to-merge/waiting-for-ci 👍
PR is good to merge, but CI hasn't passed at time of review. Please merge if you see CI has passed
and removed
reviewed/needs-rework 🔨
PR has been reviewed and needs another round of reworks
labels
Aug 30, 2021
LGTM too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
good-to-merge/waiting-for-ci 👍
PR is good to merge, but CI hasn't passed at time of review. Please merge if you see CI has passed
gpt-auto
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously volatile-root was only checked if "/" wasn't backed by a
block device, but the block device isn't necessarily original root block
device (ex: if the rootfs is copied to a ext4 fs backed by zram in the
initramfs), so we always want volatile-root checked.
So shuffle the code around so volatile-root is checked first and
fallback to the automatic logic.
Fix #20557
Tested in our Yocto image like so: