From: krzk@kernel.org (Krzysztof Kozlowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] drm/exynos: Print kernel pointers in a restricted form
Date: Tue, 14 Mar 2017 21:08:59 +0200 [thread overview]
Message-ID: <20170314190859.y55wlc4z7xdsbbxg@kozik-lap> (raw)
In-Reply-To: <e1800491-0b60-74d1-1377-756d5b0bb371@math.uni-bielefeld.de>
On Tue, Mar 14, 2017 at 08:01:41PM +0100, Tobias Jakobi wrote:
> Hello Krzysztof,
>
> I was wondering about the benefit of this. From a quick look these are
> all messages that end up in the kernel log / dmesg.
>
> IIRC %pK does nothing there, since dmest_restrict is supposed to be used
> to deny an unpriviliged user the access to the kernel log.
>
> Or am I missing something here?
These are regular printks so depending on kernel options (e.g. dynamic
debug, drm.debug) these might be printed also in the console. Of course
we could argue then if access to one of the consoles is worth
securing.
Actually, I think that we should get rid of printing of these kernel
pointers entirely...
Best regards,
Krzysztof
next prev parent reply other threads:[~2017-03-14 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170314183912epcas4p2731fbe283583ca0e0183de39694dacfc@epcas4p2.samsung.com>
2017-03-14 18:38 ` [PATCH] drm/exynos: Print kernel pointers in a restricted form Krzysztof Kozlowski
2017-03-14 19:01 ` Tobias Jakobi
2017-03-14 19:08 ` Krzysztof Kozlowski [this message]
2017-03-14 19:17 ` Tobias Jakobi
2017-03-14 19:52 ` Krzysztof Kozlowski
2017-03-14 20:41 ` Tobias Jakobi
2017-03-15 7:32 ` Andrzej Hajda
2017-03-15 12:33 ` Tobias Jakobi
2017-03-15 4:50 ` Inki Dae
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=20170314190859.y55wlc4z7xdsbbxg@kozik-lap \
--to=krzk@kernel.org \
--cc=linux-arm-kernel@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).