Re: [PATCH] ligtnvm: if LUNs are already allocated fix return

2017-06-27 Thread Rakesh Pandit
Hi Frans, On Tue, Jun 27, 2017 at 11:06:44AM +0200, Frans Klaver wrote: > On Tue, Jun 27, 2017 at 10:39 AM, Matias Bjørling wrote: > > From: Rakesh Pandit > > > > While creating new device with NVM_DEV_CREATE if LUNs are already > > allocated ioctl would return -ENOMEM which is wrong. This patch

Re: [PATCH] ligtnvm: if LUNs are already allocated fix return

2017-06-27 Thread Frans Klaver
On Tue, Jun 27, 2017 at 10:39 AM, Matias Bjørling wrote: > From: Rakesh Pandit > > While creating new device with NVM_DEV_CREATE if LUNs are already > allocated ioctl would return -ENOMEM which is wrong. This patch > propagates -EBUSY from nvm_reserve_luns which is correct response. > > Fixes: a

Re: [PATCH] ligtnvm: if LUNs are already allocated fix return

2017-05-30 Thread Matias Bjørling
On Mon, May 29, 2017 at 11:05 AM, Rakesh Pandit wrote: > Hi Matias, > > On Mon, May 15, 2017 at 06:31:58AM +, Javier Gonzalez wrote: >> > >> > On 13 May 2017, at 21.50, Rakesh Pandit wrote: >> > >> > While creating new device with NVM_DEV_CREATE if LUNs are already >> > allocated ioctl would

Re: [PATCH] ligtnvm: if LUNs are already allocated fix return

2017-05-29 Thread Rakesh Pandit
Hi Matias, On Mon, May 15, 2017 at 06:31:58AM +, Javier Gonzalez wrote: > > > > On 13 May 2017, at 21.50, Rakesh Pandit wrote: > > > > While creating new device with NVM_DEV_CREATE if LUNs are already > > allocated ioctl would return -ENOMEM which is wrong. This patch > > propagates -EBUSY

Re: [PATCH] ligtnvm: if LUNs are already allocated fix return

2017-05-14 Thread Javier Gonzalez
> > On 13 May 2017, at 21.50, Rakesh Pandit wrote: > > While creating new device with NVM_DEV_CREATE if LUNs are already > allocated ioctl would return -ENOMEM which is wrong. This patch > propagates -EBUSY from nvm_reserve_luns which is correct response. > > Fixes: ade69e243 ("lightnvm: merge