From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
linux@roeck-us.net, shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, pavel@denx.de,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, slade@sladewatkins.com,
Larry Finger <Larry.Finger@lwfinger.net>,
Phillip Potter <phil@philpotter.co.uk>,
linux-staging@lists.linux.dev
Subject: Re: [PATCH 5.15 000/135] 5.15.51-rc1 review
Date: Wed, 29 Jun 2022 12:52:52 +0200 [thread overview]
Message-ID: <YrwvBCFAVibGVdav@kroah.com> (raw)
In-Reply-To: <Yrp3q1gpvfUm8QIP@debian.me>
On Tue, Jun 28, 2022 at 10:38:19AM +0700, Bagas Sanjaya wrote:
> On Mon, Jun 27, 2022 at 01:20:07PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.51 release.
> > There are 135 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
>
> Successfully cross-compiled for arm (multi_v7_defconfig, GCC 12.1.0,
> armv7 with neon FPU) and arm64 (bcm2711_defconfig, GCC 12.1.0).
>
> But I see a warning on arm64 build:
>
> CC [M] drivers/staging/r8188eu/core/rtw_br_ext.o
> CC [M] net/batman-adv/tvlv.o
> In function '__nat25_add_pppoe_tag',
> inlined from 'nat25_db_handle' at drivers/staging/r8188eu/core/rtw_br_ext.c:520:11:
> drivers/staging/r8188eu/core/rtw_br_ext.c:83:9: warning: 'memcpy' reading between 2052 and 9220 bytes from a region of size 40 [-Wstringop-overread]
> 83 | memcpy((unsigned char *)ph->tag, tag, data_len);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/staging/r8188eu/core/rtw_br_ext.c: In function 'nat25_db_handle':
> drivers/staging/r8188eu/core/rtw_br_ext.c:489:63: note: source object 'tag_buf' of size 40
> 489 | unsigned char tag_buf[40];
> | ^~~~~~~
>
> Introduced by commit 15865124feed88 ("staging: r8188eu: introduce new core dir
> for RTL8188eu driver").
That is due to gcc-12 stuff.
thanks for testing.
thanks,
greg k-h
prev parent reply other threads:[~2022-06-29 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220627111938.151743692@linuxfoundation.org>
2022-06-28 3:38 ` [PATCH 5.15 000/135] 5.15.51-rc1 review Bagas Sanjaya
2022-06-29 10:52 ` Greg Kroah-Hartman [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=YrwvBCFAVibGVdav@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Larry.Finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=phil@philpotter.co.uk \
--cc=shuah@kernel.org \
--cc=slade@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.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 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).