From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jon Hunter Subject: Re: [RFC PATCH V2 5/8] irqchip/gic: Return an error if GIC initialisation fails Date: Fri, 18 Dec 2015 10:24:16 +0000 Message-ID: <5673DED0.9060505@nvidia.com> References: <1450349309-8107-1-git-send-email-jonathanh@nvidia.com> <1450349309-8107-6-git-send-email-jonathanh@nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Linus Walleij Cc: Thomas Gleixner , Jason Cooper , Marc Zyngier , Jiang Liu , Stephen Warren , Thierry Reding , Kevin Hilman , Geert Uytterhoeven , Grygorii Strashko , Lars-Peter Clausen , Soren Brinkmann , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" List-Id: linux-tegra@vger.kernel.org On 17/12/15 13:26, Linus Walleij wrote: > On Thu, Dec 17, 2015 at 11:48 AM, Jon Hunter wrote: > >> If the GIC initialisation fails, then currently we do not return an error >> or clean-up afterwards. Although for root controllers, this failure may be >> fatal anyway, for secondary controllers, it may not be fatal and so return >> an error on failure and clean-up. >> >> Also for non-banked GIC controllers, make sure that we free any memory >> allocated if we fail to initialise the IRQ domain. >> >> Signed-off-by: Jon Hunter > (...) > > Almost perfect but... > >> +err: >> + if (IS_ENABLED(CONFIG_GIC_NON_BANKED) && percpu_offset) { >> + free_percpu(gic->dist_base.percpu_base); >> + free_percpu(gic->cpu_base.percpu_base); > > What if the first map worked but not the second? > > Should it be: > > if (gic->dist_base.percpu_base) > free_percpu(gic->dist_base.percpu_base); > if (gic->cpu_base.percpu_base) > free_percpu(gic->cpu_base.percpu_base); > > ? Yes this is a bit lazy, but the first thing free_percpu() checks if the pointer is NULL and simply returns. If you look at the current code in __gic_init_bases(), if one of the two fail, we still try to free both. I did not like this, but when I looked at it, I could see that is does work. Happy to change it though. Cheers Jon