From: Greg KH <gregkh@linuxfoundation.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 01/13] [3.18-stable] ARM: cns3xxx: shut up frame size warning
Date: Thu, 4 May 2017 15:27:01 -0700 [thread overview]
Message-ID: <20170504222701.GA4856@kroah.com> (raw)
In-Reply-To: <20170504205209.498721-2-arnd@arndb.de>
On Thu, May 04, 2017 at 10:51:57PM +0200, Arnd Bergmann wrote:
> This shuts up a warning in the 3.18-stable series that has been fixed
> in newer kernels with commit 498a92d42596 ("ARM: cns3xxx: pci: avoid
> potential stack overflow"):
>
> arch/arm/mach-cns3xxx/pcie.c: In function 'cns3xxx_pcie_hw_init':
> arch/arm/mach-cns3xxx/pcie.c:313:1: error: the frame size of 1080 bytes is larger than 1024 bytes [-Werror=frame-larger-than=]
>
> The fix that went into v4.4 is known to be buggy and was later
> fixed again with commit 88e9da9a2a70 ("CNS3xxx: Fix PCI
> cns3xxx_write_config()"). While we could backport both to 3.18,
> they are fairly invasive and the warning is definitely harmless
> here as the call chain is known to not overflow the stack of the
> init task.
>
> This simply adds a Makefile flag to extend the limit for this one
> file.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> We do want 88e9da9a2a70 ("CNS3xxx: Fix PCI cns3xxx_write_config()")
> backported into v4.4 though.
That's already there, thanks.
greg k-h
next prev parent reply other threads:[~2017-05-04 22:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 20:51 [PATCH 00/13] [3.18-stable] backported build fixes Arnd Bergmann
2017-05-04 20:51 ` [PATCH 01/13] [3.18-stable] ARM: cns3xxx: shut up frame size warning Arnd Bergmann
2017-05-04 22:27 ` Greg KH [this message]
2017-05-04 22:37 ` Patch "ARM: cns3xxx: shut up frame size warning" has been added to the 3.18-stable tree gregkh
2017-05-04 20:51 ` [PATCH 02/13] [3.18-stable] arm64: Provide a namespace to NCAPS Arnd Bergmann
2017-05-04 20:51 ` [PATCH 03/13] [3.18-stable] staging: vt6655: fix overly large stack usage Arnd Bergmann
2017-05-04 22:37 ` Patch "staging: vt6655: fix overly large stack usage" has been added to the 3.18-stable tree gregkh
2017-05-04 20:52 ` [PATCH 04/13] [3.18-stable] staging: imx-drm: fix indentation warning Arnd Bergmann
2017-05-04 22:37 ` Patch "staging: imx-drm: fix indentation warning" has been added to the 3.18-stable tree gregkh
2017-05-04 20:52 ` [PATCH 05/13] [3.18-stable] staging: bcm: add 32-bit host dependency Arnd Bergmann
2017-05-04 22:37 ` Patch "staging: bcm: add 32-bit host dependency" has been added to the 3.18-stable tree gregkh
2017-05-04 20:52 ` [PATCH 06/13] [3.18-stable] IB/qib: rename BITS_PER_PAGE to RVT_BITS_PER_PAGE Arnd Bergmann
2017-05-04 22:37 ` Patch "IB/qib: rename BITS_PER_PAGE to RVT_BITS_PER_PAGE" has been added to the 3.18-stable tree gregkh
2017-05-04 22:37 ` Patch "IB/qib: rename BITS_PER_PAGE to RVT_BITS_PER_PAGE" has been added to the 4.4-stable tree gregkh
2017-05-04 20:52 ` [PATCH 07/13] [3.18-stable] IB/ehca: fix maybe-uninitialized warnings Arnd Bergmann
2017-05-04 22:37 ` Patch "IB/ehca: fix maybe-uninitialized warnings" has been added to the 3.18-stable tree gregkh
2017-05-04 22:37 ` Patch "IB/ehca: fix maybe-uninitialized warnings" has been added to the 4.4-stable tree gregkh
2017-05-04 20:52 ` [PATCH 08/13] [3.18-stable] tty/isicom: fix big-endian compile warning Arnd Bergmann
2017-05-04 20:52 ` [PATCH 09/13] [3.18-stable] infiniband: mlx5: avoid a compile-time warning Arnd Bergmann
2017-05-04 20:52 ` [PATCH 10/13] [3.18-stable] ips: remove pointless #warning Arnd Bergmann
2017-05-04 20:52 ` [PATCH 11/13] [3.18-stable] mISDN: avoid arch specific __builtin_return_address call Arnd Bergmann
2017-05-04 20:52 ` [PATCH 12/13] [3.18-stable] arm64: build vdso without libgcov Arnd Bergmann
2017-05-04 20:52 ` [PATCH 13/13] [3.18-stable] mm/cma: silence warnings due to max() usage Arnd Bergmann
2017-05-04 22:39 ` [PATCH 00/13] [3.18-stable] backported build fixes Greg KH
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=20170504222701.GA4856@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=arnd@arndb.de \
--cc=stable@vger.kernel.org \
/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.