From: Joerg Roedel <joro@8bytes.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: gary.hook@amd.com, Linux IOMMU <iommu@lists.linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kbuild <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH v9 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU
Date: Tue, 25 Sep 2018 09:51:04 +0200 [thread overview]
Message-ID: <20180925075104.GA18287@8bytes.org> (raw)
In-Reply-To: <CAMuHMdVf-QDAVh-vHF_xyvX73_nsO9X7RnDc=yCK_FS68i6zTw@mail.gmail.com>
On Mon, Aug 27, 2018 at 08:56:50AM +0200, Geert Uytterhoeven wrote:
> If it is that bad, shouldn't this option be protected by some Kconfig
> trickery to avoid it being enabled in allmodconfig/allyesconfig builds?
It is fine to have it in allmodconfig/allyesconfig, I just don't want
any distro-kernel enable it so that these internals become a user-space
ABI or leak security sensitive data on everyones system. This is
intended to be a pure debugging feature for development.
Regards,
Joerg
next prev parent reply other threads:[~2018-09-25 13:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-12 21:41 [PATCH v9 0/2] Base enablement of IOMMU debugfs support Gary R Hook
2018-06-12 21:41 ` [PATCH v9 1/2] iommu - Enable debugfs exposure of IOMMU driver internals Gary R Hook
2018-06-12 21:41 ` [PATCH v9 2/2] iommu/amd: Add basic debugfs infrastructure for AMD IOMMU Gary R Hook
2018-06-14 23:56 ` Randy Dunlap
2018-08-27 6:56 ` Geert Uytterhoeven
2018-08-27 6:56 ` Geert Uytterhoeven
2018-09-25 7:51 ` Joerg Roedel [this message]
2018-07-06 12:06 ` [PATCH v9 0/2] Base enablement of IOMMU debugfs support Joerg Roedel
2018-07-06 12:06 ` Joerg Roedel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180925075104.GA18287@8bytes.org \
--to=joro@8bytes.org \
--cc=arnd@arndb.de \
--cc=gary.hook@amd.com \
--cc=geert@linux-m68k.org \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.