From: kernel test robot <lkp@intel.com>
To: "Mickaël Salaün" <mic@linux.microsoft.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
James Morris <jamorris@linux.microsoft.com>,
Kees Cook <keescook@chromium.org>, Jann Horn <jannh@google.com>
Subject: arch/x86/include/asm/string_32.h:182:25: warning: '__builtin_memcpy' specified bound 4294967295 exceeds maximum object size 2147483647
Date: Sun, 5 Nov 2023 19:51:54 +0800 [thread overview]
Message-ID: <202311051904.8hqTj5mc-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: aea6bf908d730b01bd264a8821159db9463c111c
commit: ae271c1b14de343b888e77f74f640e3dcbdeb4c9 landlock: Add ruleset and domain management
date: 2 years, 6 months ago
config: i386-buildonly-randconfig-r002-20220101 (https://download.01.org/0day-ci/archive/20231105/202311051904.8hqTj5mc-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231105/202311051904.8hqTj5mc-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/202311051904.8hqTj5mc-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/x86/include/asm/string.h:3,
from include/linux/string.h:21,
from include/linux/bitmap.h:9,
from include/linux/cpumask.h:12,
from include/linux/smp.h:13,
from include/linux/lockdep.h:14,
from security/landlock/ruleset.c:15:
security/landlock/ruleset.c: In function 'create_rule':
>> arch/x86/include/asm/string_32.h:182:25: warning: '__builtin_memcpy' specified bound 4294967295 exceeds maximum object size 2147483647 [-Wstringop-overflow=]
182 | #define memcpy(t, f, n) __builtin_memcpy(t, f, n)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
security/landlock/ruleset.c:96:9: note: in expansion of macro 'memcpy'
96 | memcpy(new_rule->layers, layers,
| ^~~~~~
vim +/__builtin_memcpy +182 arch/x86/include/asm/string_32.h
^1da177e4c3f41 include/asm-i386/string.h Linus Torvalds 2005-04-16 177
^1da177e4c3f41 include/asm-i386/string.h Linus Torvalds 2005-04-16 178 /*
^1da177e4c3f41 include/asm-i386/string.h Linus Torvalds 2005-04-16 179 * No 3D Now!
^1da177e4c3f41 include/asm-i386/string.h Linus Torvalds 2005-04-16 180 */
^1da177e4c3f41 include/asm-i386/string.h Linus Torvalds 2005-04-16 181
ff60fab71bb3b4 arch/x86/include/asm/string_32.h Arjan van de Ven 2009-09-28 @182 #define memcpy(t, f, n) __builtin_memcpy(t, f, n)
^1da177e4c3f41 include/asm-i386/string.h Linus Torvalds 2005-04-16 183
:::::: The code at line 182 was first introduced by commit
:::::: ff60fab71bb3b4fdbf8caf57ff3739ffd0887396 x86: Use __builtin_memset and __builtin_memcpy for memset/memcpy
:::::: TO: Arjan van de Ven <arjan@infradead.org>
:::::: CC: H. Peter Anvin <hpa@zytor.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-11-05 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 11:51 kernel test robot [this message]
2023-12-24 5:16 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=202311051904.8hqTj5mc-lkp@intel.com \
--to=lkp@intel.com \
--cc=jamorris@linux.microsoft.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mic@linux.microsoft.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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
all inboxes | Powered by JetHome®