linux-kernel - Re: [PATCH v3 0/5] Add debugfs info for the AMD IOMMU

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: <20180315135838.GB5259@8bytes.org>
Date:   Thu, 15 Mar 2018 14:58:38 +0100
From:   Joerg Roedel <joro@...tes.org>
To:     Gary R Hook <gary.hook@....com>
Cc:     iommu@...ts.linux-foundation.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/5] Add debugfs info for the AMD IOMMU

On Wed, Mar 14, 2018 at 06:04:44PM -0500, Gary R Hook wrote:
> Gary R Hook (5):
>       iommu/amd - Add debugfs support
>       iommu/amd - Add a 'verbose' switch for IOMMU debugfs
>       iommu/amd - Add a README variable for the IOMMU debugfs
>       iommu/amd - Expose the active IOMMU device table entries
>       iommu/amd - Add a debugfs entry to specify a IOMMU device table entry

Same problem here as with the Intel patches, I don't think it's a good
idea to reveal internal iommu data structures to user-space in this way.

I've debugged iommu issues for around 10 years now and never had the
need for an interface that reveals those internals. How exactly are you
planning to use this information?

	Joerg