Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 383333 - sys-apps/openrc-0.9.3-r1: mountinfo: realpath(): No such file or directory
Summary: sys-apps/openrc-0.9.3-r1: mountinfo: realpath(): No such file or directory
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Hosted Projects
Classification: Unclassified
Component: OpenRC (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: OpenRC Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 387433
  Show dependency tree
 
Reported: 2011-09-17 10:37 UTC by Dennis Schridde
Modified: 2011-12-31 20:22 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Reintroduce error message (mountinfo.diff,716 bytes, patch)
2011-12-31 16:45 UTC, Attila Tóth
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Schridde 2011-09-17 10:37:15 UTC
Shortly before powering off the computer, after remounting / read-only, this line is displayed on the console:
mountinfo: realpath(): No such file or directory

Reproducible: Always
Comment 1 Christian Ruppert (idl0r) gentoo-dev 2011-09-28 16:48:40 UTC
Hrm, I misread the description. What we fixed was the issue during boot, not shutdown. So marking bug as UNCONFIRMED again.
Comment 2 William Hubbs gentoo-dev 2011-11-15 21:30:21 UTC
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.
Comment 3 Attila Tóth 2011-12-31 16:45:17 UTC
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.
Comment 4 Christian Ruppert (idl0r) gentoo-dev 2011-12-31 17:14:27 UTC
Please attach the rc.log or even better a serial dump (with rc_parallel disabled).
Comment 5 SpanKY gentoo-dev 2011-12-31 20:22:26 UTC
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 ...