Bug 2572309
| Summary: | oo7 issuing warning messages as it's unable to lock pages in memory | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Artur Ruta <artur.ruta> |
| Component: | oo7 | Assignee: | Fabio Valentini <decathorpe> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 45 | CC: | alstanwood3, decathorpe, ngompa13 |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | --- | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Artur Ruta
2026-11-12 09:42:14 UTC
Confirmed that this issue remains present in oo7-0.7.2-1.fc45, installed from updates-testing. Environment: - Fedora Workstation 45, x86_64 - GNOME Shell 51.1 - Kernel 7.3.4-300.fc45.x86_64 - oo7-daemon, oo7-portal and pam_oo7: 0.7.2-1.fc45 Both memory-locking warnings continue to appear at daemon startup. Process measurements: ``` VmSize: 1848056 kB VmLck: 0 kB VmRSS: 13092 kB VmSwap: 0 kB CapEff: 0000000000000000 ``` Systemd resource limits: ``` LimitMEMLOCK=8388608 LimitMEMLOCKSoft=8388608 AmbientCapabilities= ``` The executable `/usr/libexec/oo7-daemon` has no file capabilities. The system has 32 GiB of physical RAM, approximately 17.5% memory utilization, and no swap utilization at the time of testing. No service configuration, resource limits or capabilities have been modified. This confirms that the reported behavior persists in version 0.7.2 and is also reproducible under GNOME. Thanks for the report. For now I don't think this is a "problem" per se, and that would be confirmed by oo7 just logging warnings here rather than existing with an error state, but it would be "nice" to avoid this issue and have oo7 fully work as intended.
Reading through the relevant source code of oo7 [0] and the mlockall manual page [1], the error returned by "mlockall" would indicate that oo7 tries to lock more pages than the current default limit ("ulimit -l" returns 8192 on my system, i.e. 8MiB) - I don't know if we should give oo7-daemon the necessary capabilities to circumvent this limit or not, or if that limit can be raised for oo7 somehow.
[0]: https://github.com/linux-credentials/oo7/blob/0.7.3/server/src/capability.rs#L129-L134
https://github.com/linux-credentials/oo7/blob/0.7.3/server/src/capability.rs#L165-L175
[1]: https://sourceware.org/glibc/manual/latest/html_node/Page-Lock-Functions.html#index-mlockall
|