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]
Date:   Thu, 12 Jul 2018 09:15:36 +0200
From:   Christoph Hellwig <>
To:     Joonsoo Kim <>
Cc:     Michal Hocko <>,
        Marek Szyprowski <>,
        Linux Memory Management List <>,
        LKML <>,,
        linuxppc-dev <>,,
        Andrew Morton <>,
        Michal Nazarewicz <>,
        Joonsoo Kim <>,
        Vlastimil Babka <>,
        Christoph Hellwig <>,
        Russell King <>,
        Catalin Marinas <>,
        Will Deacon <>,
        Paul Mackerras <>,
        Benjamin Herrenschmidt <>,
        Chris Zankel <>,
        Martin Schwidefsky <>,
        Joerg Roedel <>,
        Sumit Semwal <>,
        Robin Murphy <>,
        Laura Abbott <>,
Subject: Re: [PATCH 1/2] mm/cma: remove unsupported gfp_mask parameter from

On Thu, Jul 12, 2018 at 11:48:47AM +0900, Joonsoo Kim wrote:
> One of existing user is general DMA layer and it takes gfp flags that is
> provided by user. I don't check all the DMA allocation sites but how do
> you convince that none of them try to use anything other

They use a few others things still like __GFP_COMP, __GPF_DMA or
GFP_HUGEPAGE.  But all these are bogus as we have various implementations
that can't respect them.  I plan to get rid of the gfp_t argument
in the dma_map_ops alloc method in a few merge windows because of that,
but it needs further implementation consolidation first.

Powered by blists - more mailing lists