Summary: | sys-apps/openrc-0.9.3-r1: mountinfo: realpath(): No such file or directory | ||
---|---|---|---|
Product: | Gentoo Hosted Projects | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
Component: | OpenRC | Assignee: | OpenRC Team <openrc> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo.2019 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 387433 | ||
Attachments: | Reintroduce error message |
Description
Dennis Schridde
2011-09-17 10:37:15 UTC
Hrm, I misread the description. What we fixed was the issue during boot, not shutdown. So marking bug as UNCONFIRMED again. I spoke with Vapier about this, and the realpath() call should not error out when it fails in this situation. This is fixed in commit 3f2e9c4. Created attachment 297471 [details, diff]
Reintroduce error message
I hit this bug, because the Hardened policy of my system prevented /sbin/rc to access some paths. The current stable openrc (0.9.4) still contains the code giving the error message. And the error displays wrong path - maybe because realpath is called using argv[optind++] argument with side effects, while the error message has argv[0]. Because the error message is displayed at the very end of the shutdown process, I could only guess the binary and tried to accomodate the system policy. It took me a while to figure out the incorrectness of the path displayed in the error message. At least it was a bit more challenging this way. But the error message was still useful, because it notified me about some changes necessary to made in the policy.
It might be still useful to display the error message if realpath was unsuccessful and introduce the modified code in the stable ebuild as well until newer version will be stabilized.
Thx:
Dw.
Please attach the rc.log or even better a serial dump (with rc_parallel disabled). Comment on attachment 297471 [details, diff]
Reintroduce error message
this code path may not call error() helpers as those cause the program to exit. i'm indifferent about having the code call warn() though ...
|