linux-kernel - Re: [PATCH] block/swim3: Fix -EBUSY error when re-opening device after unmount

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]

Message-ID: <75422eb4-a0d7-c71d-643f-24496d86c74b@kernel.dk>
Date:   Mon, 31 Dec 2018 10:20:18 -0700
From:   Jens Axboe <axboe@...nel.dk>
To:     Finn Thain <fthain@...egraphics.com.au>
Cc:     linuxppc-dev@...ts.ozlabs.org, linux-block@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] block/swim3: Fix -EBUSY error when re-opening device
 after unmount

On 12/30/18 10:44 PM, Finn Thain wrote:
> When the block device is opened with FMODE_EXCL, ref_count is set to -1.
> This value doesn't get reset when the device is closed which means the
> device cannot be opened again. Fix this by checking for refcount <= 0
> in the release method.

Applied, thanks.


-- 
Jens Axboe