Re: [PATCH] Fix a bdi reregistration race, v3

2016-06-15 Thread Bart Van Assche
On 06/04/2016 01:25 AM, Bart Van Assche wrote: Earlier today I discovered a subtle bug in v3 of this patch. It would be appreciated if you could give v4 a try. The only substantial difference between v3 and v4 is that a "if (dev->class != &sdev_class)" test has been added. (again replying to my

Re: [PATCH] Fix a bdi reregistration race, v3

2016-06-03 Thread Bart Van Assche
On 05/09/2016 06:50 AM, Joe Lawrence wrote: > On 05/05/2016 04:40 PM, Joe Lawrence wrote: >> On 05/05/2016 03:58 PM, Bart Van Assche wrote: >>> On 03/28/2016 02:29 PM, Bart Van Assche wrote: Avoid that the sd driver registers a BDI device with a name that is still in use. This patch avoid

Re: [PATCH] Fix a bdi reregistration race, v3

2016-05-09 Thread Joe Lawrence
On 05/05/2016 04:40 PM, Joe Lawrence wrote: > On 05/05/2016 03:58 PM, Bart Van Assche wrote: >> On 03/28/2016 02:29 PM, Bart Van Assche wrote: >>> Avoid that the sd driver registers a BDI device with a name that >>> is still in use. This patch avoids that the following warning gets >>> triggered: >

Re: [PATCH] Fix a bdi reregistration race, v3

2016-05-05 Thread Joe Lawrence
On 05/05/2016 03:58 PM, Bart Van Assche wrote: > On 03/28/2016 02:29 PM, Bart Van Assche wrote: >> Avoid that the sd driver registers a BDI device with a name that >> is still in use. This patch avoids that the following warning gets >> triggered: >> >> [ ... ] > > (replying to my own e-mail) > >

Re: [PATCH] Fix a bdi reregistration race, v3

2016-05-05 Thread Bart Van Assche
On 03/28/2016 02:29 PM, Bart Van Assche wrote: Avoid that the sd driver registers a BDI device with a name that is still in use. This patch avoids that the following warning gets triggered: [ ... ] (replying to my own e-mail) If anyone could review this patch that would be very welcome. Than

[PATCH] Fix a bdi reregistration race, v3

2016-03-28 Thread Bart Van Assche
Avoid that the sd driver registers a BDI device with a name that is still in use. This patch avoids that the following warning gets triggered: WARNING: CPU: 7 PID: 203 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x68/0x80() sysfs: cannot create duplicate filename '/devices/virtual/bdi/8:32' Workqueue: eve