From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: "Tobin C. Harding" <me@tobin.cc>,
Kees Cook <keescook@chromium.org>,
Laura Abbott <labbott@redhat.com>, Jessica Yu <jeyu@redhat.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] doc: update 'unique identifiers'
Date: Tue, 5 Dec 2017 08:22:40 +1100 [thread overview]
Message-ID: <1512422560-31290-1-git-send-email-me@tobin.cc> (raw)
Advice about what to use as a unique identifier is no longer valid since
patch series was merged to hash pointers printed with %p. We can use
this as a unique identifier now.
Signed-off-by: Tobin C. Harding <me@tobin.cc>
---
Documentation/security/self-protection.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/security/self-protection.rst b/Documentation/security/self-protection.rst
index 60c8bd8b77bf..f10f47cad825 100644
--- a/Documentation/security/self-protection.rst
+++ b/Documentation/security/self-protection.rst
@@ -274,8 +274,8 @@ Unique identifiers
------------------
Kernel memory addresses must never be used as identifiers exposed to
-userspace. Instead, use an atomic counter, an idr, or similar unique
-identifier.
+userspace. Printk specifier %p hashes addresses by default now and can be
+used as a unique identifier.
Memory initialization
---------------------
--
2.7.4
next reply other threads:[~2017-12-04 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 21:22 Tobin C. Harding [this message]
2017-12-04 21:28 ` Kees Cook
2017-12-04 21:44 ` Tobin C. Harding
2017-12-04 21:51 ` Kees Cook
2017-12-04 23:39 ` Tobin C. Harding
2017-12-05 1:25 ` Kees Cook
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=1512422560-31290-1-git-send-email-me@tobin.cc \
--to=me@tobin.cc \
--cc=corbet@lwn.net \
--cc=jeyu@redhat.com \
--cc=keescook@chromium.org \
--cc=labbott@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®