linux-kernel - Re: [PATCH 3/3] dma-pool: limit DMA and DMA32 zone size pools

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]

Date:   Sun, 21 Aug 2022 12:44:16 +0200
From:   Christoph Hellwig <hch@....de>
To:     Michal Hocko <mhocko@...e.com>
Cc:     Christoph Hellwig <hch@....de>, iommu@...ts.linux.dev,
        Marek Szyprowski <m.szyprowski@...sung.com>,
        Robin Murphy <robin.murphy@....com>,
        David Rientjes <rientjes@...gle.com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/3] dma-pool: limit DMA and DMA32 zone size pools

On Wed, Aug 17, 2022 at 02:53:47PM +0200, Michal Hocko wrote:
> Yes this is much more reasonable estimation. Especially for the DMA
> zone. I still believe some downscaling would make sense but as said
> earlier nothing to really insist on. Also you likely want to have
> pr_warn for non-poppulated DMA zone as pointed in other thread[1].

So I think the warning would be useful, but how do we detect that the
zone should exist and is empty vs the case where it doesn't even
exist based on a runtime decision?