From: kernel test robot <lkp@intel.com>
To: Jeffrey Hugo <quic_jhugo@quicinc.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Carl Vanderlip <quic_carlv@quicinc.com>,
Pranjal Ramajor Asha Kanojiya <quic_pkanojiy@quicinc.com>,
Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>
Subject: drivers/accel/qaic/qaic_control.c:348:17: warning: array subscript 'struct wrapper_msg[0]' is partly outside array bounds of 'unsigned char[44]'
Date: Wed, 20 Sep 2023 04:55:05 +0800 [thread overview]
Message-ID: <202309200403.mGPrZFN4-lkp@intel.com> (raw)
Hi Jeffrey,
First bad commit (maybe != root cause):
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 2cf0f715623872823a72e451243bbf555d10d032
commit: 759662e4f1f8cd6ea0ec466e10cf29fe7c1fec36 accel/qaic: Add qaic driver to the build system
date: 6 months ago
config: i386-randconfig-i015-20230718 (https://download.01.org/0day-ci/archive/20230920/202309200403.mGPrZFN4-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/20230920/202309200403.mGPrZFN4-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/202309200403.mGPrZFN4-lkp@intel.com/
All warnings (new ones prefixed by >>):
In function 'add_wrapper',
inlined from 'abort_dma_cont' at drivers/accel/qaic/qaic_control.c:1107:12,
inlined from 'qaic_manage_msg_xfer' at drivers/accel/qaic/qaic_control.c:1165:9:
>> drivers/accel/qaic/qaic_control.c:348:17: warning: array subscript 'struct wrapper_msg[0]' is partly outside array bounds of 'unsigned char[44]' [-Warray-bounds]
348 | w->head = wrappers;
| ~~~~~~~~^~~~~~~~~~
In file included from include/linux/fs.h:45,
from include/linux/huge_mm.h:8,
from include/linux/mm.h:855,
from include/linux/scatterlist.h:8,
from include/linux/dma-mapping.h:10,
from drivers/accel/qaic/qaic_control.c:10:
In function 'kmalloc',
inlined from 'kzalloc' at include/linux/slab.h:720:9,
inlined from 'add_wrapper' at drivers/accel/qaic/qaic_control.c:342:26,
inlined from 'abort_dma_cont' at drivers/accel/qaic/qaic_control.c:1107:12,
inlined from 'qaic_manage_msg_xfer' at drivers/accel/qaic/qaic_control.c:1165:9:
include/linux/slab.h:580:24: note: object of size 44 allocated by 'kmalloc_trace'
580 | return kmalloc_trace(
| ^~~~~~~~~~~~~~
581 | kmalloc_caches[kmalloc_type(flags)][index],
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
582 | flags, size);
| ~~~~~~~~~~~~
In function 'abort_dma_cont',
inlined from 'qaic_manage_msg_xfer' at drivers/accel/qaic/qaic_control.c:1165:9:
drivers/accel/qaic/qaic_control.c:1121:22: warning: array subscript 'struct wrapper_msg[0]' is partly outside array bounds of 'unsigned char[44]' [-Warray-bounds]
1121 | wrapper->len = size;
| ~~~~~~~~~~~~~^~~~~~
In function 'kmalloc',
inlined from 'kzalloc' at include/linux/slab.h:720:9,
inlined from 'add_wrapper' at drivers/accel/qaic/qaic_control.c:342:26,
inlined from 'abort_dma_cont' at drivers/accel/qaic/qaic_control.c:1107:12,
inlined from 'qaic_manage_msg_xfer' at drivers/accel/qaic/qaic_control.c:1165:9:
include/linux/slab.h:580:24: note: object of size 44 allocated by 'kmalloc_trace'
580 | return kmalloc_trace(
| ^~~~~~~~~~~~~~
581 | kmalloc_caches[kmalloc_type(flags)][index],
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
582 | flags, size);
| ~~~~~~~~~~~~
vim +348 drivers/accel/qaic/qaic_control.c
129776ac2e3823 Jeffrey Hugo 2023-03-27 339
129776ac2e3823 Jeffrey Hugo 2023-03-27 340 static struct wrapper_msg *add_wrapper(struct wrapper_list *wrappers, u32 size)
129776ac2e3823 Jeffrey Hugo 2023-03-27 341 {
129776ac2e3823 Jeffrey Hugo 2023-03-27 342 struct wrapper_msg *w = kzalloc(size, GFP_KERNEL);
129776ac2e3823 Jeffrey Hugo 2023-03-27 343
129776ac2e3823 Jeffrey Hugo 2023-03-27 344 if (!w)
129776ac2e3823 Jeffrey Hugo 2023-03-27 345 return NULL;
129776ac2e3823 Jeffrey Hugo 2023-03-27 346 list_add_tail(&w->list, &wrappers->list);
129776ac2e3823 Jeffrey Hugo 2023-03-27 347 kref_init(&w->ref_count);
129776ac2e3823 Jeffrey Hugo 2023-03-27 @348 w->head = wrappers;
129776ac2e3823 Jeffrey Hugo 2023-03-27 349 return w;
129776ac2e3823 Jeffrey Hugo 2023-03-27 350 }
129776ac2e3823 Jeffrey Hugo 2023-03-27 351
:::::: The code at line 348 was first introduced by commit
:::::: 129776ac2e38231fa9c02ce20e116c99de291666 accel/qaic: Add control path
:::::: TO: Jeffrey Hugo <quic_jhugo@quicinc.com>
:::::: CC: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-19 20:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 20:55 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-18 14:42 drivers/accel/qaic/qaic_control.c:348:17: warning: array subscript 'struct wrapper_msg[0]' is partly outside array bounds of 'unsigned char[44]' 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=202309200403.mGPrZFN4-lkp@intel.com \
--to=lkp@intel.com \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_carlv@quicinc.com \
--cc=quic_jhugo@quicinc.com \
--cc=quic_pkanojiy@quicinc.com \
--cc=stanislaw.gruszka@linux.intel.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 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.