linux-kernel - Re: [PATCH v2] scsi: Don't call memset after dma_alloc

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200902160337.kvuujxodeokrbn4d@medion>
Date:   Wed, 2 Sep 2020 17:03:37 +0100
From:   Alex Dewar <alex.dewar90@...il.com>
To:     "Martin K. Petersen" <martin.petersen@...cle.com>
Cc:     Alex Dewar <alex.dewar90@...il.com>,
        GR-QLogic-Storage-Upstream@...vell.com, jejb@...ux.ibm.com,
        linux-kernel@...r.kernel.org, linux-scsi@...r.kernel.org,
        njavali@...vell.com
Subject: Re: [PATCH v2] scsi: Don't call memset after dma_alloc_coherent()

On Tue, Sep 01, 2020 at 09:22:44PM -0400, Martin K. Petersen wrote:
> 
> Alex,
> 
> > dma_alloc_coherent() already zeroes memory, so the extra call to
> > memset() is unnecessary.
> 
> One patch per driver, please.

Nvm, someone's already beaten me to the punch!
> 
> Thanks!
> 
> -- 
> Martin K. Petersen	Oracle Linux Engineering