Re: [PATCH] enclosure: fix sysfs symlinks creation when using multipath

Dne 21.3.2017 v 10:58 Maurizio Lombardi napsal(a): > I will ask our customer to test your patch, > there is only a small problem: you can't set cdev->dev = NULL > and then call enclosure_add_links(cdev) because you will end up dereferencing > a NULL pointer. > I suggest a slightly different

Re: [PATCH] enclosure: fix sysfs symlinks creation when using multipath

Dne 16.3.2017 v 19:49 James Bottomley napsal(a): > diff --git a/drivers/misc/enclosure.c b/drivers/misc/enclosure.c > index 65fed71..ae89082 100644 > --- a/drivers/misc/enclosure.c > +++ b/drivers/misc/enclosure.c > @@ -375,6 +375,7 @@ int enclosure_add_device(struct enclosure_device *edev, >

Re: [PATCH] enclosure: fix sysfs symlinks creation when using multipath

On Wed, 2017-03-15 at 19:39 -0400, Martin K. Petersen wrote: > Maurizio Lombardi writes: > > > With multipath, it may happen that the same device is passed to > > enclosure_add_device() multiple times and that the > > enclosure_add_links() function fails to create the

Re: [PATCH] enclosure: fix sysfs symlinks creation when using multipath

Maurizio Lombardi writes: > With multipath, it may happen that the same device is passed to > enclosure_add_device() multiple times and that the > enclosure_add_links() function fails to create the symlinks because > the device's sysfs directory entry is still NULL. In this

[PATCH] enclosure: fix sysfs symlinks creation when using multipath

With multipath, it may happen that the same device is passed to enclosure_add_device() multiple times and that the enclosure_add_links() function fails to create the symlinks because the device's sysfs directory entry is still NULL. In this case, the links will never be created because all the