linux-kernel - Re: dma_zalloc_coherent broken with 57bf5a8963f80fb3828c46c3e3a5b2dd790e09a7

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:   Wed, 28 Mar 2018 13:57:03 +0200
From:   Christoph Hellwig <hch@....de>
To:     Sebastian Ott <sebott@...ux.vnet.ibm.com>
Cc:     Christoph Hellwig <hch@....de>,
        Jesper Nilsson <jesper.nilsson@...s.com>,
        Geert Uytterhoeven <geert@...ux-m68k.org>,
        linux-kernel@...r.kernel.org
Subject: Re: dma_zalloc_coherent broken with
        57bf5a8963f80fb3828c46c3e3a5b2dd790e09a7

On Tue, Mar 27, 2018 at 07:04:51PM +0200, Sebastian Ott wrote:
> What was wrong with the old behavior (let the caller decide - the same
> as with memory allocations)?

The old behavior on most (all?) mainstream architectures is that we
always zero the return value.  On x86/i386 this goes back to at least
Linux 2.4.  So common drivers simply expect this to happen.