mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: Petr Mladek <pmladek@suse.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Kernel development list <linux-kernel@vger.kernel.org>
Subject: Printk specifiers for __user pointers
Date: Fri, 20 Nov 2020 11:44:12 -0500	[thread overview]
Message-ID: <20201120164412.GD619708@rowland.harvard.edu> (raw)

To the VSPRINTF maintainers:

Documentation/core-api/printk-formats.rst lists a large number of format 
specifiers for pointers of various sorts.  Yet as far as I can see, 
there is no specifier meant for use with __user pointers.

The security implications of printing the true, unmangled value of a 
__user pointer are minimal, since doing so does not leak any kernel 
information.  So %px would work, but tools like checkpatch.pl don't like 
it.

Should a new specifier be added?  If not, should we simply use %px?

Alan Stern

             reply	other threads:[~2020-11-20 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 16:44 Alan Stern [this message]
2020-11-20 18:42 ` Steven Rostedt
2020-11-23  9:53   ` Petr Mladek
2020-11-23 14:11     ` Steven Rostedt
2020-11-24 21:53     ` 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=20201120164412.GD619708@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    --cc=rostedt@goodmis.org \
    --cc=sergey.senozhatsky@gmail.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 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®