Recently, the nodedev driver gained ability to define (some type of)
devices. However, it uncovered some dormant bugs we had (patches 2/5 and
3/5) and also introduced some (patches 1/5 and 5/5).

I've came across these problems because I don't have /etc/mdevctl.d on
my machine.

Michal Prívozník (5):
  nodedev: Unlock @priv if initialization of mdevctlMonitors fails
  nodedev: Lock @priv sooner
  nodedev: Don't join not spawned threads
  nodedev: Separate mdevctl monitor setup into a function
  nodedev: Only set up mdevctl monitors if mdevctl.d exist

 src/node_device/node_device_udev.c | 75 ++++++++++++++++++++----------
 1 file changed, 51 insertions(+), 24 deletions(-)

-- 
2.26.3

On Mon, Apr 12, 2021 at 06:22:19PM +0200, Michal Privoznik wrote:
> Recently, the nodedev driver gained ability to define (some type of)
> devices. However, it uncovered some dormant bugs we had (patches 2/5 and
> 3/5) and also introduced some (patches 1/5 and 5/5).
> 
> I've came across these problems because I don't have /etc/mdevctl.d on
> my machine.
> 
> Michal Prívozník (5):
>   nodedev: Unlock @priv if initialization of mdevctlMonitors fails
>   nodedev: Lock @priv sooner
>   nodedev: Don't join not spawned threads
>   nodedev: Separate mdevctl monitor setup into a function
>   nodedev: Only set up mdevctl monitors if mdevctl.d exist

With the comment for last patch fixed:

Reviewed-by: Pavel Hrdina <phrdina@redhat.com>