From: Jonathan Corbet <corbet@lwn.net>
To: Jiri Kosina <jkosina@suse.cz>
Cc: David Howells <dhowells@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] MODSIGN: /proc/keys is not unconditionally available
Date: Wed, 28 Jan 2015 12:12:07 -0700 [thread overview]
Message-ID: <20150128121207.59254055@lwn.net> (raw)
In-Reply-To: <alpine.LNX.2.00.1501131555510.4162@pobox.suse.cz>
On Tue, 13 Jan 2015 15:57:10 +0100 (CET)
Jiri Kosina <jkosina@suse.cz> wrote:
> Documentation/module-signing.txt file is referring to /proc/keys file in
> order to view all keys contained in the kernel's keyring. That file is not
> universally avialble when CONFIG_KEYS is enabled, which is confusing. The
> fact that the option needed for this procfs interface to exist contains
> "_DEBUG_" in its name makes it even more confusing. Document this fact.
Applied to the docs tree, thanks.
jon
next prev parent reply other threads:[~2015-01-28 20:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-13 14:57 [PATCH] MODSIGN: /proc/keys is not unconditionally available Jiri Kosina
2015-01-22 20:42 ` Jiri Kosina
2015-01-22 22:28 ` David Howells
2015-01-23 10:50 ` Jiri Kosina
2015-01-28 19:12 ` Jonathan Corbet [this message]
2015-01-28 19:20 ` David Howells
2015-01-28 19:33 ` Jonathan Corbet
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=20150128121207.59254055@lwn.net \
--to=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=jkosina@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox