Red Hat Bugzilla – Bug 1310780
RFC: Add dnf plugin to detect processes running with deleted shared libraries (or reboot required).
Last modified: 2017-12-07 19:06:31 EST
The recent glibc CVE-2015-7547 has raised a number of interesting issues when it comes to upgrading. Users have chosen not to reboot per the "reboot suggested" (not required), have been failing to restart dependent processes, and have been filing bugs when their processes fail (not robust against dlopen failures or process startup failures).
I can make two recommendations:
(a) Add a "reboot required" to bodhi and dnf. This is used only as a last resort for critical security issues that require a new kernel or core runtime and everything depends upon it. When an update is installed that requires an update a dnf core plugin would keep warning the user that they need to reboot. This could be done at every subsequent dnf operation.
(b) Add a dnf plugin which scans all running processes on the system in the current process namespace (or in a target namespace if dnf is being used to act upon a container) and detects if any are using deleted shared libraries e.g. /proc/$PID/map_files contains deleted entries. At that point the plugin should recommend a restart of those processes because of the deleted shared libraries which are still mapped into the process. This warning should not be seen for files the user installs and deletes, just for shared libraries which are part of packages controlled by the package manager.
This would greatly help the situation and keep users aware that they have processes or systems that need restarting.
It should be noted that this may interact with systemd cgroups, and may need some systemd integration also for a high-quality implementation, but I'm not sure if that is immediately required.
Note that there is a dnf-tracer plugin: http://dnf-plugins-extras.readthedocs.org/en/latest/tracer.html.
$ sudo dnf install 'dnf-command(tracer)'
$ sudo dnf tracer
You should restart:
Nothing needs to be restarted
Though recommendation (a) would be nice as well (or maybe even have `dnf update` automatically run `dnf tracer` after the transaction).
Actually, from the docs on that page, it seems to do that already (i.e. runs `tracer` after every transaction). Though on my machine, I have to run it manually (probably not using the latest version or something).
(In reply to Jonathan Lebon from comment #3)
> Actually, from the docs on that page, it seems to do that already (i.e. runs
> `tracer` after every transaction). Though on my machine, I have to run it
> manually (probably not using the latest version or something).
Thanks for that post! Yes, it might mean that we should adopt tracer in some way into the core set of plugins which are enabled. Users need to know what needs restarting IMO. They simply don't pay attention to anything else other than warnings from dnf.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
DNF tracer plugin was created by community. Reassigning to plugins extras component to check whether tracer plugin really runs after the transaction.
We don't plan to move tracer plugin into plugins core but you can add tracer plugin alone to base Fedora image (probably needs approval of FESCo).
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
Problem still remains in Rawhide. We should have a way to detect processes running with old libraries and inform the user of them.