From: Dan Carpenter <dan.carpenter@linaro.org>
To: kernel test robot <lkp@intel.com>
Cc: Dan Carpenter <error27@gmail.com>,
Steffen Klassert <steffen.klassert@secunet.com>,
oe-kbuild-all@lists.linux.dev,
Herbert Xu <herbert@gondor.apana.org.au>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH net] xfrm: fix integer overflow in xfrm_replay_state_esn_len()
Date: Thu, 30 Jan 2025 11:16:43 +0300 [thread overview]
Message-ID: <f86c7660-0910-4ca2-9ff9-d2d142a968c7@stanley.mountain> (raw)
In-Reply-To: <202501230035.cFbLTHtZ-lkp@intel.com>
I've added linux-hardening to the CC.
This is a fortify false positive. I can't reproduce it on x86 with
gcc-14. Perhaps it only affect mips? It's a W=1 warning so it shouldn't
be a blocker in that sense.
regards,
dan carpenter
On Thu, Jan 23, 2025 at 12:53:14AM +0800, kernel test robot wrote:
> Hi Dan,
>
> kernel test robot noticed the following build warnings:
>
> [auto build test WARNING on net/main]
>
> url: https://github.com/intel-lab-lkp/linux/commits/Dan-Carpenter/xfrm-fix-integer-overflow-in-xfrm_replay_state_esn_len/20250121-191827
> base: net/main
> patch link: https://lore.kernel.org/r/018ecf13-e371-4b39-8946-c7510baf916b%40stanley.mountain
> patch subject: [PATCH net] xfrm: fix integer overflow in xfrm_replay_state_esn_len()
> config: mips-allyesconfig (https://download.01.org/0day-ci/archive/20250123/202501230035.cFbLTHtZ-lkp@intel.com/config)
> compiler: mips-linux-gcc (GCC) 14.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250123/202501230035.cFbLTHtZ-lkp@intel.com/reproduce)
>
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202501230035.cFbLTHtZ-lkp@intel.com/
>
> All warnings (new ones prefixed by >>):
>
> In file included from include/linux/string.h:389,
> from include/linux/bitmap.h:13,
> from include/linux/cpumask.h:12,
> from arch/mips/include/asm/processor.h:15,
> from arch/mips/include/asm/thread_info.h:16,
> from include/linux/thread_info.h:60,
> from include/asm-generic/preempt.h:5,
> from ./arch/mips/include/generated/asm/preempt.h:1,
> from include/linux/preempt.h:79,
> from include/linux/spinlock.h:56,
> from include/net/xfrm.h:7,
> from net/xfrm/xfrm_replay.c:10:
> In function 'memcmp',
> inlined from 'xfrm_replay_notify_bmp' at net/xfrm/xfrm_replay.c:336:7:
> >> include/linux/fortify-string.h:120:33: warning: '__builtin_memcmp' specified bound 4294967295 exceeds maximum object size 2147483647 [-Wstringop-overread]
> 120 | #define __underlying_memcmp __builtin_memcmp
> | ^
> include/linux/fortify-string.h:727:16: note: in expansion of macro '__underlying_memcmp'
> 727 | return __underlying_memcmp(p, q, size);
> | ^~~~~~~~~~~~~~~~~~~
> net/xfrm/xfrm_replay.c: In function 'xfrm_replay_notify_bmp':
> net/xfrm/xfrm_replay.c:308:53: note: source object allocated here
> 308 | struct xfrm_replay_state_esn *replay_esn = x->replay_esn;
> | ~^~~~~~~~~~~~
> In function 'memcmp',
> inlined from 'xfrm_replay_notify_esn' at net/xfrm/xfrm_replay.c:402:7:
> >> include/linux/fortify-string.h:120:33: warning: '__builtin_memcmp' specified bound 4294967295 exceeds maximum object size 2147483647 [-Wstringop-overread]
> 120 | #define __underlying_memcmp __builtin_memcmp
> | ^
> include/linux/fortify-string.h:727:16: note: in expansion of macro '__underlying_memcmp'
> 727 | return __underlying_memcmp(p, q, size);
> | ^~~~~~~~~~~~~~~~~~~
> net/xfrm/xfrm_replay.c: In function 'xfrm_replay_notify_esn':
> net/xfrm/xfrm_replay.c:360:53: note: source object allocated here
> 360 | struct xfrm_replay_state_esn *replay_esn = x->replay_esn;
> | ~^~~~~~~~~~~~
>
>
> vim +/__builtin_memcmp +120 include/linux/fortify-string.h
>
> 78a498c3a227f2 Alexander Potapenko 2022-10-24 118
> 78a498c3a227f2 Alexander Potapenko 2022-10-24 119 #define __underlying_memchr __builtin_memchr
> 78a498c3a227f2 Alexander Potapenko 2022-10-24 @120 #define __underlying_memcmp __builtin_memcmp
> a28a6e860c6cf2 Francis Laniel 2021-02-25 121 #define __underlying_strcat __builtin_strcat
> a28a6e860c6cf2 Francis Laniel 2021-02-25 122 #define __underlying_strcpy __builtin_strcpy
> a28a6e860c6cf2 Francis Laniel 2021-02-25 123 #define __underlying_strlen __builtin_strlen
> a28a6e860c6cf2 Francis Laniel 2021-02-25 124 #define __underlying_strncat __builtin_strncat
> a28a6e860c6cf2 Francis Laniel 2021-02-25 125 #define __underlying_strncpy __builtin_strncpy
> 2e577732e8d28b Andrey Konovalov 2024-05-17 126
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-01-30 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 11:16 [PATCH net] xfrm: fix integer overflow in xfrm_replay_state_esn_len() Dan Carpenter
2025-01-22 12:39 ` Simon Horman
2025-01-22 13:16 ` Dan Carpenter
2025-01-22 13:50 ` Dan Carpenter
2025-01-22 16:53 ` kernel test robot
2025-01-30 8:16 ` Dan Carpenter [this message]
2025-01-31 20:28 ` kernel test robot
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=f86c7660-0910-4ca2-9ff9-d2d142a968c7@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=edumazet@google.com \
--cc=error27@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=horms@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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