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

core/manager: run generators directly when we are in initrd #26494

Closed

Conversation

yuwata
Copy link
Member

@yuwata yuwata commented Feb 20, 2023

Some initrd system write files at ourside of /run, /etc, or other allowed places. This is a kind of workaround, but in most cases, such sandboxing is not necessary as the filesystem is on ramfs when we are in initrd.

Fixes #26488.

Some initrd system write files at ourside of /run, /etc, or other
allowed places. This is a kind of workaround, but in most cases, such
sandboxing is not necessary as the filesystem is on ramfs when we are in
initrd.

Fixes systemd#26488.
@yuwata yuwata added the pid1 label Feb 20, 2023
@yuwata yuwata requested a review from keszybz February 20, 2023 03:03
@github-actions github-actions bot added the please-review PR is ready for (re-)review by a maintainer label Feb 20, 2023
@poettering
Copy link
Member

This doesn't look right. The goal of the sandboxing was to trip up generators "with side-effects", i.e. that write files outside of the generator output dirs.

So the right fix is to fix those generators, not work around them in our code, neither in the initrd nor elsewhere.

@keszybz keszybz removed the please-review PR is ready for (re-)review by a maintainer label Feb 20, 2023
@yuwata
Copy link
Member Author

yuwata commented Feb 20, 2023

OK. Thank you for the comments.

I initially thought that we should postpone to apply the sandbox in initrd to give a time to dracut or other initrd build tools to update their generators. But, if we postpone the change, it is easily expected that no change will come until we re-apply the sandbox.

Closing.

@yuwata yuwata closed this Feb 20, 2023
@yuwata yuwata deleted the core-run-generators-directly-in-initrd branch February 20, 2023 21:38
gerrit-photon pushed a commit to vmware/photon that referenced this pull request Mar 29, 2023
lvm with latest systemd and dracut doesn't boot up.
Upstream issues for reference:
  - dracut: dracutdevs/dracut#2211
  - systemd: systemd/systemd#26488

Temporary patch applied until this issue is resolved
systemd/systemd#26494

See systemd/systemd#26488 (comment)

Change-Id: I1964ff2a82b7c2d6c53e02b4368a8d5d6f9a03a1
Signed-off-by: Tapas Kundu <tkundu@vmware.com>
Reviewed-on: http://photon-jenkins.eng.vmware.com:8082/20134
gerrit-photon pushed a commit to vmware/photon that referenced this pull request Mar 31, 2023
lvm with latest systemd and dracut doesn't boot up.
Upstream issues for reference:
  - dracut: dracutdevs/dracut#2211
  - systemd: systemd/systemd#26488

Temporary patch applied until this issue is resolved
systemd/systemd#26494

See systemd/systemd#26488 (comment)

Change-Id: I1964ff2a82b7c2d6c53e02b4368a8d5d6f9a03a1
Reviewed-on: http://photon-jenkins.eng.vmware.com:8082/20132
Tested-by: gerrit-photon <photon-checkins@vmware.com>
Reviewed-by: Susant Sahani <ssahani@vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

Boot failure regression 253 (Bisected) (lvm at fault)
3 participants