From: Marc Zyngier <marc.zyngier@arm.com>
To: Matt Redfearn <matt.redfearn@imgtec.com>,
Arvind Yadav <arvind.yadav.cs@gmail.com>,
tglx@linutronix.de, jason@lakedaemon.net
Cc: linux-kernel@vger.kernel.org,
Linux MIPS Mailing List <linux-mips@linux-mips.org>
Subject: Re: [PATCH v1] irqchip: irq-mips-gic:- Handle return NULL error from ioremap_nocache
Date: Tue, 17 Jan 2017 10:25:29 +0000 [thread overview]
Message-ID: <7b1e2045-9e3c-7101-8750-1c6db90e5953@arm.com> (raw)
In-Reply-To: <574c27a3-cee8-6649-ef20-9903a1d9850d@imgtec.com>
On 17/01/17 10:17, Matt Redfearn wrote:
>
>
> On 17/01/17 10:10, Arvind Yadav wrote:
>> Hi Matt,
>>
>> Please Acknowledge this.
>>
>> Regards
>> Arvind Yadav
>
> Hi Arvind,
>
> Acked-by: Matt Redfearn <matt.redfearn@imgtec.com>
>
>
>>
>> On Monday 09 January 2017 02:30 PM, Marc Zyngier wrote:
>>> On 09/01/17 08:08, Arvind Yadav wrote:
>>>> Here, If ioremap_nocache will fail. It will return NULL.
>>>> Kernel can run into a NULL-pointer dereference.
>>>> This error check will avoid NULL pointer dereference.
>>>>
>>>> Signed-off-by: Arvind Yadav <arvind.yadav.cs@gmail.com>
>>>> ---
>>>> drivers/irqchip/irq-mips-gic.c | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/drivers/irqchip/irq-mips-gic.c
>>>> b/drivers/irqchip/irq-mips-gic.c
>>>> index c01c09e..eeea2e8 100644
>>>> --- a/drivers/irqchip/irq-mips-gic.c
>>>> +++ b/drivers/irqchip/irq-mips-gic.c
>>>> @@ -979,6 +979,8 @@ static void __init __gic_init(unsigned long
>>>> gic_base_addr,
>>>> __gic_base_addr = gic_base_addr;
>>>> gic_base = ioremap_nocache(gic_base_addr, gic_addrspace_size);
>>>> + if (!gic_base)
>>>> + panic("Failed to map GIC memory");
>>> So you're replacing a panic due to dereferencing a NULL pointer with
>>> another panic -- not much progress here. I appreciate that the message
>>> is a bit more explicit, but is there something slightly less drastic we
>>> could do? Like returning an error code and see if the kernel otherwise
>>> recovers (possibly with reduced functionality)?
>
> Marc, there's really not much that can be done without the GIC
> initializing sucessfully. This should not happen if platform code /
> device tree is set up correctly, so an explicit panic if that is not the
> case is helpful.
Fair enough, that's your call. I'll pick that up as is.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2017-01-17 10:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 8:08 Arvind Yadav
2017-01-09 9:00 ` Marc Zyngier
2017-01-17 10:10 ` Arvind Yadav
2017-01-17 10:17 ` Matt Redfearn
2017-01-17 10:25 ` Marc Zyngier [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=7b1e2045-9e3c-7101-8750-1c6db90e5953@arm.com \
--to=marc.zyngier@arm.com \
--cc=arvind.yadav.cs@gmail.com \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=matt.redfearn@imgtec.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®