rfkill: treat ENXIO/ENODEV the same way as ENOENT
authorLennart Poettering <lennart@poettering.net>
Thu, 5 Apr 2018 10:43:08 +0000 (12:43 +0200)
committerLennart Poettering <lennart@poettering.net>
Thu, 5 Apr 2018 11:00:43 +0000 (13:00 +0200)
commitbc5e002ef1728f45871d2b0344e3f04108db62c7
tree73db422c6955672f6fb97f5e3a79e25538da46d5
parent3b3d1737be0023791e45dfa357b347c832d2a615
rfkill: treat ENXIO/ENODEV the same way as ENOENT

If an rfkill device disappears between the time we get notified about
the existance and we fully opened it we might get ENXIO or ENODEV (i.e.
the two kinds of "device not found" errors, which are typically
generated when for example a device node has no actual backing device
behind it). let's handle that the same way as ENOENT, and downgrade the
log message to LOG_DEBUG.

Fixes: #8586
src/rfkill/rfkill.c