linux-kernel - Re: Passing NULL dev to 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] [day] [month] [year] [list]

Message-ID: <20200628071014.GA16213@lst.de>
Date:   Sun, 28 Jun 2020 09:10:14 +0200
From:   Christoph Hellwig <hch@....de>
To:     Richard Weinberger <richard@....at>
Cc:     iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
        sumit.semwal@...aro.org, robin.murphy@....com,
        m.szyprowski@...sung.com, hch@....de, dan.carpenter@...cle.com
Subject: Re: Passing NULL dev to dma_alloc_coherent() allowed or not?

You can't pass NULL.  The synclink case is dead code as we stopped
supporting non-PCI adapters a while ago.  I had a patch to remove
the !PCI code a while ago, but it seems like it never made it upstream.

The staging code is, well .. staging code.