device: don't emit PropetiesChanged needlessly

Functions called from device_setup_unit() already make sure that unit is
enqueued in case it is a new unit or properties exported on the bus have
changed.

This should prevent unnecessary DBus wakeups and associated DBus traffic
when device_setup_unit() was called while reparsing /proc/self/mountinfo
due to the mountinfo notifications. Note that we parse
/proc/self/mountinfo quite often on the busy systems (e.g. k8s container
hosts) but majority of the time mounts didn't change, only some mount
got added. Thus we don't need to generate PropertiesChanged for devices
associated with the mounts that didn't change.

Thanks to Renaud Métrich <rmetrich@redhat.com> for debugging the
problem and providing draft version of the patch.

(cherry picked from commit 2e129d5d6bd6bd8be4b5359e81a880cbf72a44b8)

Resolves: #1793533
1 file changed
tree: c6f68ae71d2adf44411a8117866db16a18d34ea3
  1. .dir-locals.el
  2. .editorconfig
  3. .gitattributes
  4. .github/
  5. .gitignore
  6. .lgtm.yml
  7. .lgtm/cpp-queries/
  8. .mailmap
  9. .mkosi/
  10. .travis.yml
  11. .vimrc
  12. .ycm_extra_conf.py
  13. LICENSE.GPL2
  14. LICENSE.LGPL2.1
  15. Makefile
  16. NEWS
  17. README
  18. README.md
  19. TODO
  20. catalog/
  21. ci/
  22. coccinelle/
  23. configure
  24. doc/
  25. factory/etc/
  26. hwdb/
  27. man/
  28. meson.build
  29. meson_options.txt
  30. mkosi.build
  31. modprobe.d/
  32. network/
  33. po/
  34. presets/
  35. rules/
  36. shell-completion/
  37. src/
  38. sysctl.d/
  39. sysusers.d/
  40. test/
  41. tmpfiles.d/
  42. tools/
  43. travis-ci/
  44. units/
  45. xorg/
  46. zanata.xml
README.md

systemd - System and Service Manager

Build Status
Coverity Scan Status
CII Best Practices
Build Status

Details

General information about systemd can be found in the systemd Wiki.

Information about build requirements are provided in the README file.

Consult our NEWS file for information about what's new in the most recent systemd versions.

Please see the HACKING file for information how to hack on systemd and test your modifications.

Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.

When preparing patches for systemd, please follow our Coding Style Guidelines.

If you are looking for support, please contact our mailing list or join our IRC channel.

Stable branches with backported patches are available in the stable repo.