linux-kernel - Re: [PATCH V3] lightnvm: if LUNs are already allocated fix return

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Tue, 27 Jun 2017 08:22:31 -0600
From:   Jens Axboe <axboe@...com>
To:     Rakesh Pandit <rakesh@...era.com>,
        Matias Bjørling <m@...rling.me>
CC:     <linux-block@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        Matias Bjørling <matias@...xlabs.com>,
        Frans Klaver <fransklaver@...il.com>,
        Javier González <jg@...htnvm.io>
Subject: Re: [PATCH V3] lightnvm: if LUNs are already allocated fix return

On 06/27/2017 05:55 AM, 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.

Thanks, applied for 4.13.

-- 
Jens Axboe