for the init-bottom/udevd script. This could be considered to be a fix for this bug.
There is still the question of extending the scope of this bug. IMHO any failure within the initramfs phase is worth a 'panic'. This would even make the point of adding 'panic' to the call_scripts function within scripts/functions for cases when a called script returns with error code.
(N.B. For testing, I tried to unconditionally call 'panic' in init-bottom/udev, but it just said something like "panic: command not found". The system did boot normally!)
According to a pointer from Steve Langasek and the manpage of initramfs-tools(5) one can do:
/sbin/frobnicate "/dev/mapper/frobb" || panic "Frobnication failed"
which translates to
udevadm control --exit || panic "udev exit failed (http:// some-wiki- page)"
for the init-bottom/udevd script. This could be considered to be a fix for this bug.
There is still the question of extending the scope of this bug. IMHO any failure within the initramfs phase is worth a 'panic'. This would even make the point of adding 'panic' to the call_scripts function within scripts/functions for cases when a called script returns with error code.
(N.B. For testing, I tried to unconditionally call 'panic' in init-bottom/udev, but it just said something like "panic: command not found". The system did boot normally!)