From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
<linux-kernel@vger.kernel.org>, <guohanjun@huawei.com>
Subject: Re: [PATCH] irqchip/mbigen: stop printing kernel addresses
Date: Tue, 18 Jun 2019 16:35:53 +0800 [thread overview]
Message-ID: <d529faf2-9edd-8362-c208-fd1902d539e7@huawei.com> (raw)
In-Reply-To: <86h88npc47.wl-marc.zyngier@arm.com>
On 2019/6/18 15:48, Marc Zyngier wrote:
> Hi Kefeng,
>
> On Tue, 18 Jun 2019 04:22:02 +0100,
> Kefeng Wang <wangkefeng.wang@huawei.com> wrote:
>>
>> After commit ad67b74d2469d9b8 ("printk: hash addresses printed with %p"),
>> it will print "____ptrval____" instead of actual addresses when mbigen
>> create domain fails,
>>
>> Hisilicon MBIGEN-V2 HISI0152:00: Failed to create mbi-gen@(____ptrval____) irqdomain
>> Hisilicon MBIGEN-V2: probe of HISI0152:00 failed with error -12
>>
>> Instead of changing the print to "%px", and leaking kernel addresses,
>> just remove the print completely.
>>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>> drivers/irqchip/irq-mbigen.c | 3 +--
>> 1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> diff --git a/drivers/irqchip/irq-mbigen.c b/drivers/irqchip/irq-mbigen.c
>> index 98b6e1d4b1a6..d0cf596c801b 100644
>> --- a/drivers/irqchip/irq-mbigen.c
>> +++ b/drivers/irqchip/irq-mbigen.c
>> @@ -355,8 +355,7 @@ static int mbigen_device_probe(struct platform_device *pdev)
>> err = -EINVAL;
>>
>> if (err) {
>> - dev_err(&pdev->dev, "Failed to create mbi-gen@%p irqdomain",
>> - mgn_chip->base);
>> + dev_err(&pdev->dev, "Failed to create mbi-gen irqdomain");
>
> The alternative would be to print res as a resource, which would still
> help identifying the offending device by printing its physical
> layout, and still not reveal much.
It's better to print res to show the physical layout, and add missing "\n",
will resend v2.
Thanks.
>
> Just let me know what you prefer.
>
> Thanks,
>
> M.
>
>> return err;
>> }
>>
>> --
>> 2.20.1
>>
>
next prev parent reply other threads:[~2019-06-18 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 3:22 Kefeng Wang
2019-06-18 7:48 ` Marc Zyngier
2019-06-18 8:35 ` Kefeng Wang [this message]
2019-06-18 8:42 ` Marc Zyngier
2019-06-18 9:08 ` Kefeng Wang
2019-06-18 7:59 ` Hanjun Guo
2019-06-18 9:15 ` [PATCH v2] " Kefeng Wang
2019-06-18 9:23 ` Hanjun Guo
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=d529faf2-9edd-8362-c208-fd1902d539e7@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=guohanjun@huawei.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
/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®