Rivoreo Source Code Repositories
src.rivoreo.one / systemd-stable / v239-23
commit966ecf0011a02c7823083a7868b8589fdf850be8[log] [download]
authorLennart Poettering <lennart@poettering.net>Mon Jan 21 20:20:35 2019 +0100
committerThe Plumber <50238977+systemd-rhel-bot@users.noreply.github.com>Wed Dec 18 13:25:41 2019 +0100
tree61d9f2ecd1a4dbcaeb844bdbf7b51148325e262d
parent3bbacfb22a9266769a41dee6f8f594fbeb6287fc [diff]
cryptsetup: rework how we log about activation failures

First of all let's always log where the errors happen, and not in an
upper stackframe, in all cases. Previously we'd do this somethis one way
and sometimes another, which resulted in sometimes duplicate logging and
sometimes none.

When we cannot activate something due to bad password the kernel gives
us EPERM. Let's uniformly return this EAGAIN, so tha the next password
is tried. (previously this was done in most cases but not in all)

When we get EPERM let's also explicitly indicate that this probably
means the password is simply wrong.

Fixes: #11498
(cherry picked from commit 6f177c7dc092eb68762b4533d41b14244adb2a73)

Related: #1776408
1 file changed
tree: 61d9f2ecd1a4dbcaeb844bdbf7b51148325e262d
  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. mkosi.default ⇨ .mkosi/mkosi.fedora
  32. modprobe.d/
  33. network/
  34. po/
  35. presets/
  36. rules/
  37. shell-completion/
  38. src/
  39. sysctl.d/
  40. sysusers.d/
  41. test/
  42. tmpfiles.d/
  43. tools/
  44. travis-ci/
  45. units/
  46. xorg/
  47. 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.