linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: maarten.lankhorst@linux.intel.com (Maarten Lankhorst)
To: linux-snps-arc@lists.infradead.org
Subject: [PATCH] drm: Print unadorned pointers
Date: Wed, 18 Apr 2018 12:08:57 +0200	[thread overview]
Message-ID: <432801bd-a775-5b48-00c4-2160ae52c25b@linux.intel.com> (raw)
In-Reply-To: <1524045595.3198.11.camel@synopsys.com>

Op 18-04-18 om 11:59 schreef Alexey Brodkin:
> On Wed, 2018-04-18@11:29 +0200, Maarten Lankhorst wrote:
>> Op 18-04-18 om 11:24 schreef Alexey Brodkin:
>>> After commit ad67b74 ("printk: hash addresses printed with %p")
>>> pointers are being hashed when printed. However, this makes
>>> debug output completely useless. Switch to %px in order to see the
>>> unadorned kernel pointers.
>>>
>>> This was done with the following one-liner:
>>>  find drivers/gpu/drm -type f -name "*.c" -exec sed -r -i '/DRM_DEBUG|KERN_DEBUG|pr_debug/ s/%p\b/%px/g' {} +
>> So first we plug a kernel information leak hole, then we introduce it again? Seems like a terrible idea..
> Well security concerns are good but what about us poor kernel developers?
> Those debug prints are supposed to help us to deal with stuff we develop or fix.
>
> Frankly I was quite surprised when first saw what was "unique hashed ID" instead
> of real pointer value. And what's worse there's no way to get previous behavior back.
> So now we have to manually patch sources here and there to get meaningful data, right?
>
> I wouldn't bother sending this patch if there was Kconfig option reverting %p behavior
> but that was never implemented.
>
> -Alexey

There's %pK for kernel pointers. It does what you want and can be toggled with kptr_restrict, without introducing security holes. :)

Perhaps split up this patch per driver, and handle the other variations as well?

DRM_NOTE DRM_WARN DRM_INFO DRM_ERROR.


~Maarten

      reply	other threads:[~2018-04-18 10:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180418092450.13798-1-abrodkin@synopsys.com>
     [not found] ` <f5acc637-6743-f3ed-9328-f7b7177d4be6@linux.intel.com>
2018-04-18  9:59   ` [PATCH] drm: Print unadorned pointers Alexey Brodkin
2018-04-18 10:08     ` Maarten Lankhorst [this message]

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=432801bd-a775-5b48-00c4-2160ae52c25b@linux.intel.com \
    --to=maarten.lankhorst@linux.intel.com \
    --cc=linux-snps-arc@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).