linux-kernel - Re: [PATCH] swiotlb: Clean up some coding style and minor issues

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]

Message-ID: <YtrAsjp0Fs0ThBa7@infradead.org>
Date:   Fri, 22 Jul 2022 08:22:26 -0700
From:   Christoph Hellwig <hch@...radead.org>
To:     Tianyu Lan <ltykernel@...il.com>
Cc:     hch@...radead.org, m.szyprowski@...sung.com, robin.murphy@....com,
        michael.h.kelley@...rosoft.com, Tianyu Lan <tiala@...rosoft.com>,
        iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
        linux-hyperv@...r.kernel.org
Subject: Re: [PATCH] swiotlb: Clean up some coding style and minor issues

I've applied this, but then dropped the debugfs changes.  I can't find
any good reason why we'd use the _unsafe variant here.  Can you resend
that bit and write a commit log clearly documenting the considerations
for it?