Lennart Poettering 6f177c7dc0 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		2019-01-23 23:37:17 +01:00
..
cryptsetup-generator.c	generators: define custom main func definer and use it where applicable	2018-12-12 21:58:00 +01:00
cryptsetup.c	cryptsetup: rework how we log about activation failures	2019-01-23 23:37:17 +01:00