From: Marc Gonzalez <marc.w.gonzalez@free.fr>
To: Vinod Koul <vkoul@kernel.org>, Fuqian Huang <huangfq.daxian@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
MSM <linux-arm-msm@vger.kernel.org>,
DMA <dmaengine@vger.kernel.org>
Subject: Re: Potential info leak: Kernel pointer leak?
Date: Wed, 23 Jan 2019 16:01:14 +0100 [thread overview]
Message-ID: <3409b71f-9b92-5e53-e87e-1486f493a55e@free.fr> (raw)
In-Reply-To: <20190123122429.GO4635@vkoul-mobl>
On 23/01/2019 13:24, Vinod Koul wrote:
> On 22-01-19, 21:25, Fuqian Huang wrote:
>
>> Recently I came across some code and it seems to be able to leak kernel address?
>> Is the following code cause info leak in the Linux kernel?
>> linux-4.14.90
>
> Doesn't %p not print kernel addresses anymore, see
> Documentation/core-api/printk-formats.rst
Commit ad67b74d2469d9b82aaa ("printk: hash addresses printed with %p")
was merged in v4.15-rc2 and not backported to v4.14 AFAICT.
Regards.
prev parent reply other threads:[~2019-01-23 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 13:25 Fuqian Huang
2019-01-23 12:24 ` Vinod Koul
2019-01-23 15:01 ` Marc Gonzalez [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=3409b71f-9b92-5e53-e87e-1486f493a55e@free.fr \
--to=marc.w.gonzalez@free.fr \
--cc=dmaengine@vger.kernel.org \
--cc=huangfq.daxian@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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®