nodedev: ignore EINVAL from libudev in udevEventHandleThread
nodedev: ignore EINVAL from libudev in udevEventHandleThread

Certain udev entries might be of a size that makes libudev emit EINVAL
which right now leads to udevEventHandleThread exiting. Due to no more
handling events other elements of libvirt will start pushing for events
to be consumed which never happens causing a busy loop burning a cpu
without any gain.

After evaluation of the example case discussed in in #245 and a test
run ignoring EINVAL it was considered safe to add EINVAL to the ignored
errnos to not exit udevEventHandleThread giving it more resilience.

The root cause is in systemd and by now was discussed and fixed via
https://github.com/systemd/systemd/issues/24987, but hardening libvirt
to be able to better deal with EINVAL returned still is the right thing
to avoid the reported busy loops on systemd with older systemd versions.

Fixes: https://gitlab.com/libvirt/libvirt/-/issues/245

Signed-off-by: Christian Ehrhardt <48da28e2c2cd455d60e19b14c46925e20a3c5d5b@canonical.com>
Reviewed-by: Daniel P. Berrangé <bb938cf255e055ff3507f2627d214e8e62118fcf@redhat.com>

jfehlig/libvirt,jfehlig/libvirt,olafhering/libvirt,libvirt/libvirt,zippy2/libvirt,libvirt/libvirt,jfehlig/libvirt,libvirt/libvirt,libvirt/libvirt,olafhering/libvirt,zippy2/libvirt,zippy2/libvirt,olafhering/libvirt,jfehlig/libvirt,olafhering/libvirt,zippy2/libvirt