From: Lee Jones <lee.jones@linaro.org>
To: Jay Aurabind <mail@aurabindo.in>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Samuel Ortiz <sameo@linux.intel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
kbuild test robot <fengguang.wu@intel.com>
Subject: Re: [PATCH V2] mfd: abx500-core: Fix compiler warning larger stack frame
Date: Thu, 22 May 2014 09:42:42 +0100 [thread overview]
Message-ID: <20140522084242.GN6679@lee--X1> (raw)
In-Reply-To: <537CE03A.7060702@aurabindo.in>
> >> Inorder to report the kzalloc failure, I have just used a pr_debug statement. If it looks ugly, should I change the function's return value to int and give out an -ENOMEM ?
> >
> > Yes, please do that - and obviously add the checks to the calling code.
>
> But I cannot find any calling code. At least thats what linux cross reference has to say.
Okay, thanks.
I've applied this patch and removed the other.
> Change from V2 -> V3:
> Change abx500_dump_all_banks to return int so as to account for error handling.
>
> Change from V1 -> V2:
> Fix a potential null pointer dereference as reported by kbuild test robot <fengguang.wu@intel.com>.
>
> From 19d34af7240498b2e624e94b2d003f3d9928dee8 Mon Sep 17 00:00:00 2001
> From: Aurabindo J <mail@aurabindo.in>
> Date: Wed, 21 May 2014 22:27:30 +0530
> Subject: [PATCH] mfd: abx500-core: Fix compiler warning larger stack frame
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> On systems with CONFIG_FRAME_WARN=1024, compiler warns the allocation of
> an object of struct device on stack. Make the allocation dynamically to
> fix the warning. Also change the caller's return type to int so as to
> account for error handling.
>
> drivers/mfd/abx500-core.c: In function ‘abx500_dump_all_banks’:
> drivers/mfd/abx500-core.c:167:1: warning: the frame size of 1032 bytes
> is larger than 1024 bytes [-Wframe-larger-than=]
>
> Signed-off-by: Aurabindo J <mail@aurabindo.in>
> ---
> drivers/mfd/abx500-core.c | 12 ++++++++----
> include/linux/mfd/abx500.h | 2 +-
> 2 files changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/mfd/abx500-core.c b/drivers/mfd/abx500-core.c
> index f3a15aa..d6d0ec4 100644
> --- a/drivers/mfd/abx500-core.c
> +++ b/drivers/mfd/abx500-core.c
> @@ -151,19 +151,23 @@ int abx500_startup_irq_enabled(struct device *dev, unsigned int irq)
> }
> EXPORT_SYMBOL(abx500_startup_irq_enabled);
>
> -void abx500_dump_all_banks(void)
> +int abx500_dump_all_banks(void)
> {
> struct abx500_ops *ops;
> - struct device dummy_child = {NULL};
> + struct device *dummy_child;
> struct abx500_device_entry *dev_entry;
>
> + dummy_child = kzalloc(sizeof(struct device), GFP_KERNEL);
> + if (!dummy_child)
> + return -ENOMEM;
> list_for_each_entry(dev_entry, &abx500_list, list) {
> - dummy_child.parent = dev_entry->dev;
> + dummy_child->parent = dev_entry->dev;
> ops = &dev_entry->ops;
>
> if ((ops != NULL) && (ops->dump_all_banks != NULL))
> - ops->dump_all_banks(&dummy_child);
> + ops->dump_all_banks(dummy_child);
> }
> + kfree(dummy_child);
> }
> EXPORT_SYMBOL(abx500_dump_all_banks);
>
> diff --git a/include/linux/mfd/abx500.h b/include/linux/mfd/abx500.h
> index 3301b20..df2508f 100644
> --- a/include/linux/mfd/abx500.h
> +++ b/include/linux/mfd/abx500.h
> @@ -330,7 +330,7 @@ int abx500_mask_and_set_register_interruptible(struct device *dev, u8 bank,
> int abx500_get_chip_id(struct device *dev);
> int abx500_event_registers_startup_state_get(struct device *dev, u8 *event);
> int abx500_startup_irq_enabled(struct device *dev, unsigned int irq);
> -void abx500_dump_all_banks(void);
> +int abx500_dump_all_banks(void);
>
> struct abx500_ops {
> int (*get_chip_id) (struct device *);
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2014-05-22 8:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 12:02 [PATCH] mfd: abx500-core: Fix compiler warning larger stack frame Jay Aurabind
2014-05-20 15:20 ` Lee Jones
2014-05-21 6:15 ` [PATCH V2] " Jay Aurabind
2014-05-21 9:17 ` Lee Jones
2014-05-21 17:19 ` Jay Aurabind
2014-05-22 8:42 ` Lee Jones [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=20140522084242.GN6679@lee--X1 \
--to=lee.jones@linaro.org \
--cc=fengguang.wu@intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@aurabindo.in \
--cc=sameo@linux.intel.com \
/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