From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: drivers/net/ethernet/via/via-velocity.c:3615 velocity_get_strings() error: __builtin_memcpy() '*velocity_gstrings' too small (32 vs 1024)
Date: Sun, 15 Dec 2024 00:50:30 +0800 [thread overview]
Message-ID: <202412150045.roY0gOfb-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Andrey Konovalov <andreyknvl@gmail.com>
CC: Andrew Morton <akpm@linux-foundation.org>
CC: Linux Memory Management List <linux-mm@kvack.org>
CC: Marco Elver <elver@google.com>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a446e965a188ee8f745859e63ce046fe98577d45
commit: 2e577732e8d28b9183df701fb90cb7943aa4ed16 kasan, fortify: properly rename memintrinsics
date: 7 months ago
:::::: branch date: 15 hours ago
:::::: commit date: 7 months ago
config: x86_64-randconfig-161-20241212 (https://download.01.org/0day-ci/archive/20241215/202412150045.roY0gOfb-lkp@intel.com/config)
compiler: clang version 19.1.3 (https://github.com/llvm/llvm-project ab51eccf88f5321e7c60591c5546b254b6afab99)
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202412150045.roY0gOfb-lkp@intel.com/
smatch warnings:
drivers/net/ethernet/via/via-velocity.c:3615 velocity_get_strings() error: __builtin_memcpy() '*velocity_gstrings' too small (32 vs 1024)
vim +3615 drivers/net/ethernet/via/via-velocity.c
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3610
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3611 static void velocity_get_strings(struct net_device *dev, u32 sset, u8 *data)
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3612 {
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3613 switch (sset) {
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3614 case ETH_SS_STATS:
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 @3615 memcpy(data, *velocity_gstrings, sizeof(velocity_gstrings));
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3616 break;
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3617 }
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3618 }
ad66fa7a704f179 drivers/net/via-velocity.c françois romieu 2011-08-04 3619
:::::: The code at line 3615 was first introduced by commit
:::::: ad66fa7a704f179fd3f88dece544e2d18078860f via-velocity : ethtool statistics support.
:::::: TO: françois romieu <romieu@fr.zoreil.com>
:::::: CC: David S. Miller <davem@davemloft.net>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-12-14 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 16:50 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-12 14:28 drivers/net/ethernet/via/via-velocity.c:3615 velocity_get_strings() error: __builtin_memcpy() '*velocity_gstrings' too small (32 vs 1024) 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=202412150045.roY0gOfb-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.