From: Naresh Kamboju <naresh.kamboju@linaro.org>
To: open list <linux-kernel@vger.kernel.org>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, linux-usb@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
lkft-triage@lists.linaro.org
Cc: Nick Terrell <terrelln@fb.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>,
"David S. Miller" <davem@davemloft.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
cai.huoqing@linux.dev, Anders Roxell <anders.roxell@linaro.org>
Subject: [next] warning: the frame size of 1120 bytes is larger than 1024 bytes [-Wframe-larger-than=]
Date: Wed, 2 Mar 2022 12:13:49 +0530 [thread overview]
Message-ID: <CA+G9fYvUHjwU9sOMs+zNwuauGLqah3Ce_5VKtifZucOuXqw2qA@mail.gmail.com> (raw)
Following warnings noticed while building Linux next-20220301
for arm KASAN builds [1].
Build warnings:
lib/zstd/common/entropy_common.c: In function 'HUF_readStats':
lib/zstd/common/entropy_common.c:257:1: warning: the frame size of
1120 bytes is larger than 1024 bytes [-Wframe-larger-than=]
257 | }
| ^
net/ipv4/tcp.c: In function 'do_tcp_getsockopt.constprop':
net/ipv4/tcp.c:4272:1: warning: the frame size of 1152 bytes is larger
than 1024 bytes [-Wframe-larger-than=]
4272 | }
| ^
fs/select.c: In function 'do_sys_poll':
fs/select.c:1045:1: warning: the frame size of 1264 bytes is larger
than 1024 bytes [-Wframe-larger-than=]
1045 | }
| ^
drivers/usb/host/xhci.c: In function 'xhci_reserve_bandwidth':
drivers/usb/host/xhci.c:2877:1: warning: the frame size of 1056 bytes
is larger than 1024 bytes [-Wframe-larger-than=]
2877 | }
| ^
drivers/media/dvb-frontends/mxl5xx.c: In function 'config_ts':
drivers/media/dvb-frontends/mxl5xx.c:1566:1: warning: the frame size
of 1224 bytes is larger than 1024 bytes [-Wframe-larger-than=]
1566 | }
| ^
Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
Steps to reproduce:
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
tuxmake --runtime podman --target-arch arm --toolchain gcc-10
--kconfig https://builds.tuxbuild.com/25mUEFdMf8eGt8sUkh7JnHahLIW/config
--
Linaro LKFT
https://lkft.linaro.org
[1] https://builds.tuxbuild.com/25mUEFdMf8eGt8sUkh7JnHahLIW/
next reply other threads:[~2022-03-02 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 6:43 Naresh Kamboju [this message]
2022-03-02 14:19 ` [next] warning: the frame size of 1120 bytes is larger than 1024 bytes [-Wframe-larger-than=] Matthew Wilcox
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=CA+G9fYvUHjwU9sOMs+zNwuauGLqah3Ce_5VKtifZucOuXqw2qA@mail.gmail.com \
--to=naresh.kamboju@linaro.org \
--cc=anders.roxell@linaro.org \
--cc=ast@kernel.org \
--cc=cai.huoqing@linux.dev \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mathias.nyman@intel.com \
--cc=mchehab@kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=terrelln@fb.com \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).