linux-kernel - Re: fix up nowarn confusion in the dma mapping layer

Open Source and information security mailing list archives

Message-ID: <8da56b4f-0625-cb44-fa21-d7c1c04a56b0@arm.com>
Date:   Tue, 9 Oct 2018 13:55:03 +0100
From:   Robin Murphy <robin.murphy@....com>
To:     Christoph Hellwig <hch@....de>, iommu@...ts.linux-foundation.org
Cc:     linux-kernel@...r.kernel.org
Subject: Re: fix up nowarn confusion in the dma mapping layer

On 08/10/18 08:03, Christoph Hellwig wrote:
> Any comments on these rather trivial patches?

Nope ;)

For both,
Acked-by: Robin Murphy <robin.murphy@....com>

> On Mon, Oct 01, 2018 at 01:12:55PM -0700, Christoph Hellwig wrote:
>> Hi all,
>>
>> this series sorts out how we deal with the nowarn flags in the dma
>> mapping code.  We still support __GFP_NOWARN for the legacy APIs that
>> don't support passing the dma specific flags, but we generally want
>> every implementation to actually check DMA_ATTR_NO_WARN instead.
>> _______________________________________________
>> iommu mailing list
>> iommu@...ts.linux-foundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/iommu
> ---end quoted text---
>

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