From: Kees Cook <keescook@chromium.org>
To: Emese Revfy <re.emese@gmail.com>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 bytes is larger than 1024 bytes
Date: Tue, 18 Oct 2016 13:57:35 -0700 [thread overview]
Message-ID: <CAGXu5j++E0VKf9Vvn0YC+GDU-Bdtu4O0NM9wdbxJM9nZVWJ7sA@mail.gmail.com> (raw)
In-Reply-To: <20161017233752.68d20a89dbc9b0ff8841c9b3@gmail.com>
On Mon, Oct 17, 2016 at 2:37 PM, Emese Revfy <re.emese@gmail.com> wrote:
> On Sun, 16 Oct 2016 06:52:16 +0800
> kbuild test robot <fengguang.wu@intel.com> wrote:
>
>> drivers/pci/hotplug/ibmphp_ebda.c: In function 'ibmphp_access_ebda':
>> >> drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 bytes is larger than 1024 bytes [-Wframe-larger-than=]
>
> Hi,
>
> Thanks for the report. The problem is that these are large functions
> (there are a lot of basic blocks) and the entropy plugin instruments all basic blocks.
> I think the solution is to skip these functions which contain more than n basic blocks.
> Sorry, I haven't time to fix this bug. PaX Team will fix it in PaX.
This is controlled by CONFIG_FRAME_WARN. I don't think this is a
particular problem or should be avoided, but perhaps we can set the
default to 2048 (as done on 64BIT) if we're building with the entropy
plugin.
-Kees
--
Kees Cook
Nexus Security
next prev parent reply other threads:[~2016-10-18 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-15 22:52 drivers/pci/hotplug/ibmphp_ebda.c:409:1: warning: the frame size of 1108 bytes is larger than 1024 bytes kbuild test robot
2016-10-17 21:37 ` Emese Revfy
2016-10-18 20:57 ` Kees Cook [this message]
2016-10-18 21:36 ` Emese Revfy
2016-10-18 22:05 ` Kees Cook
2016-10-18 22:17 ` Emese Revfy
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=CAGXu5j++E0VKf9Vvn0YC+GDU-Bdtu4O0NM9wdbxJM9nZVWJ7sA@mail.gmail.com \
--to=keescook@chromium.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=re.emese@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.