linux-kernel - Re: [PATCH] null_blk: add support for max open/active zone limit for zoned devices

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]

Date:   Thu, 27 Aug 2020 13:45:11 +0000
From:   Niklas Cassel <Niklas.Cassel@....com>
To:     Damien Le Moal <Damien.LeMoal@....com>
CC:     Jens Axboe <axboe@...nel.dk>,
        Johannes Thumshirn <Johannes.Thumshirn@....com>,
        "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] null_blk: add support for max open/active zone limit for
 zoned devices

On Tue, Aug 25, 2020 at 11:03:58PM +0000, Damien Le Moal wrote:
> On 2020/08/26 7:52, Damien Le Moal wrote:
> > On 2020/08/25 21:22, Niklas Cassel wrote:

(snip)

> Arg. No, you can't. There is the trace call after the switch. So please ignore
> this comment :)
> 
> But you can still avoid repeating the "if (ret != BLK_STS_OK) return ret;" by
> calling the trace only for BLK_STS_OK and returning ret at the end.

Agreed.

Thank you for your review comments, much appreciated.

Will send out a V2 shortly.


Kind regards,
Niklas