linux-kernel - Re: [PATCH] dma-debug: fix displaying of dma allocation type

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: <20200408191644.GA12239@lst.de>
Date:   Wed, 8 Apr 2020 21:16:44 +0200
From:   Christoph Hellwig <hch@....de>
To:     Grygorii Strashko <grygorii.strashko@...com>
Cc:     Christoph Hellwig <hch@....de>,
        Marek Szyprowski <m.szyprowski@...sung.com>,
        Robin Murphy <robin.murphy@....com>,
        iommu@...ts.linux-foundation.org, Sekhar Nori <nsekhar@...com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dma-debug: fix displaying of dma allocation type

On Wed, Apr 08, 2020 at 10:13:55PM +0300, Grygorii Strashko wrote:
>>>   -static const char *type2name[5] = { "single", "page",
>>> +static const char *type2name[5] = { "single",
>>>   				    "scather-gather", "coherent",
>>>   				    "resource" };
>>
>> To make sure this doesn't happen anymore, can you switch to
>> named initializers?
>>
>
> Just to clarify.
> Do you mean
> [dma_debug_coherent] = "coherent",
> ?

Yes.