linux-kernel - Re: [PATCH v2 1/1] null_blk: synchronization fix for zoned device

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 for Android: free password hash cracker in your pocket

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

Message-ID: <c948100e-7e01-5f30-721a-7ed8c820a3b8@kernel.dk>
Date:   Tue, 27 Oct 2020 20:40:59 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Kanchan Joshi <joshi.k@...sung.com>, Damien.LeMoal@....com
Cc:     linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
        stable@...r.kernel.org, selvakuma.s1@...sung.com,
        nj.shetty@...sung.com, javier.gonz@...sung.com
Subject: Re: [PATCH v2 1/1] null_blk: synchronization fix for zoned device

On 9/28/20 3:55 AM, Kanchan Joshi wrote:
> Parallel write,read,zone-mgmt operations accessing/altering zone state
> and write-pointer may get into race. Avoid the situation by using a new
> spinlock for zoned device.
> Concurrent zone-appends (on a zone) returning same write-pointer issue
> is also avoided using this lock.

Applied, thanks.

-- 
Jens Axboe