From: kernel test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-hardening@vger.kernel.org,
linux-bluetooth@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:pending-fixes] BUILD SUCCESS WITH WARNING bb8b9a4857726b532eaaa9d31c8acfb451227fbf
Date: Thu, 18 Aug 2022 20:02:26 +0800 [thread overview]
Message-ID: <62fe2a52.MDlOyFV1+MFSyOaw%lkp@intel.com> (raw)
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git pending-fixes
branch HEAD: bb8b9a4857726b532eaaa9d31c8acfb451227fbf Merge branch 'for-linux-next-fixes' of git://anongit.freedesktop.org/drm/drm-misc
Warning reports:
https://lore.kernel.org/linux-mm/202208110453.zEneXTnn-lkp@intel.com
Warning: (recently discovered and may have been fixed)
arch/m68k/include/asm/string.h:64:25: warning: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Wstringop-overread]
include/linux/fortify-string.h:44:33: warning: '__builtin_memcmp' specified bound 6 exceeds source size 0 [-Wstringop-overread]
include/net/bluetooth/bluetooth.h:347:16: warning: 'memcmp' specified bound 6 exceeds source size 0 [-Wstringop-overread]
Warning ids grouped by kconfigs:
gcc_recent_errors
|-- m68k-allmodconfig
| `-- arch-m68k-include-asm-string.h:warning:__builtin_memcmp-specified-bound-exceeds-source-size
|-- m68k-allyesconfig
| `-- arch-m68k-include-asm-string.h:warning:__builtin_memcmp-specified-bound-exceeds-source-size
|-- m68k-randconfig-r031-20220818
| `-- arch-m68k-include-asm-string.h:warning:__builtin_memcmp-specified-bound-exceeds-source-size
|-- mips-allyesconfig
| `-- include-linux-fortify-string.h:warning:__builtin_memcmp-specified-bound-exceeds-source-size
`-- openrisc-randconfig-r013-20220818
`-- include-net-bluetooth-bluetooth.h:warning:memcmp-specified-bound-exceeds-source-size
elapsed time: 722m
configs tested: 58
configs skipped: 2
gcc tested configs:
x86_64 randconfig-a004
arc allyesconfig
x86_64 randconfig-a002
i386 defconfig
arm defconfig
alpha allyesconfig
um x86_64_defconfig
x86_64 defconfig
m68k allyesconfig
um i386_defconfig
m68k allmodconfig
x86_64 randconfig-a006
x86_64 randconfig-a013
x86_64 randconfig-a011
arm allyesconfig
x86_64 rhel-8.3
arm64 allyesconfig
x86_64 randconfig-a015
i386 randconfig-a001
i386 randconfig-a003
x86_64 rhel-8.3-func
x86_64 rhel-8.3-kunit
x86_64 rhel-8.3-kselftests
arc randconfig-r043-20220818
i386 randconfig-a005
x86_64 rhel-8.3-syz
i386 allyesconfig
x86_64 rhel-8.3-kvm
x86_64 allyesconfig
s390 randconfig-r044-20220818
powerpc allnoconfig
powerpc allmodconfig
riscv randconfig-r042-20220818
mips allyesconfig
i386 randconfig-a014
sh allmodconfig
i386 randconfig-a012
i386 randconfig-a016
ia64 allmodconfig
arc allnoconfig
alpha allnoconfig
csky allnoconfig
riscv allnoconfig
clang tested configs:
x86_64 randconfig-a005
x86_64 randconfig-a001
x86_64 randconfig-a003
x86_64 randconfig-a012
x86_64 randconfig-a016
x86_64 randconfig-a014
i386 randconfig-a002
i386 randconfig-a004
i386 randconfig-a006
hexagon randconfig-r041-20220818
hexagon randconfig-r045-20220818
i386 randconfig-a013
i386 randconfig-a011
i386 randconfig-a015
x86_64 rhel-8.3-rust
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-08-18 12:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=62fe2a52.MDlOyFV1+MFSyOaw%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.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