From: kernel test robot <yujie.liu@intel.com>
To: Mihail Chindris <mihail.chindris@analog.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-iio@vger.kernel.org>
Cc: <clang-built-linux@googlegroups.com>, <kbuild-all@lists.01.org>,
<lars@metafoo.de>, <Michael.Hennerich@analog.com>,
<jic23@kernel.org>, <nuno.sa@analog.com>,
<dragos.bogdan@analog.com>, <alexandru.ardelean@analog.com>
Subject: Re: [PATCH v4 1/6] iio: Add output buffer support
Date: Wed, 25 Aug 2021 23:31:59 +0800 [thread overview]
Message-ID: <9837998f-9177-b32f-d71a-e1f1caa2fae2@intel.com> (raw)
In-Reply-To: <202108222341.6RtluiRt-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 4019 bytes --]
Hi Mihail,
I love your patch! Perhaps something to improve:
[auto build test WARNING on 94a853eca720ac9e385e59f27e859b4a01123f58]
url: https://github.com/0day-ci/linux/commits/Mihail-Chindris/iio-Add-output-buffer-support-and-DAC-example/20210821-010349
base: 94a853eca720ac9e385e59f27e859b4a01123f58
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: x86_64-randconfig-c007-20210822 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 9e9d70591e72fc6762b4b9a226b68ed1307419bf)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/b4f124803ed8bfe5936c756ed4c7aa9124a1468a
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Mihail-Chindris/iio-Add-output-buffer-support-and-DAC-example/20210821-010349
git checkout b4f124803ed8bfe5936c756ed4c7aa9124a1468a
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 clang-analyzer
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
clang-analyzer warnings: (new ones prefixed by >>)
>> drivers/iio/industrialio-buffer.c:325:9: warning: Called function pointer is null (null dereference) [clang-analyzer-core.CallAndMessage]
return buffer->access->remove_from(buffer, data);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/iio/industrialio-buffer.c:322:6: note: Assuming 'buffer' is non-null
if (!buffer || !buffer->access || buffer->access->remove_from)
^~~~~~~
drivers/iio/industrialio-buffer.c:322:6: note: Left side of '||' is false
drivers/iio/industrialio-buffer.c:322:17: note: Assuming field 'access' is non-null
if (!buffer || !buffer->access || buffer->access->remove_from)
^~~~~~~~~~~~~~~
drivers/iio/industrialio-buffer.c:322:6: note: Left side of '||' is false
if (!buffer || !buffer->access || buffer->access->remove_from)
^
drivers/iio/industrialio-buffer.c:322:36: note: Assuming field 'remove_from' is null
if (!buffer || !buffer->access || buffer->access->remove_from)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/iio/industrialio-buffer.c:322:6: note: Assuming pointer value is null
if (!buffer || !buffer->access || buffer->access->remove_from)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/iio/industrialio-buffer.c:322:2: note: Taking false branch
if (!buffer || !buffer->access || buffer->access->remove_from)
^
drivers/iio/industrialio-buffer.c:325:9: note: Called function pointer is null (null dereference)
return buffer->access->remove_from(buffer, data);
^~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +325 drivers/iio/industrialio-buffer.c
d2f0a48f36aea3 Lars-Peter Clausen 2013-10-04 319
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 320 int iio_buffer_remove_sample(struct iio_buffer *buffer, u8 *data)
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 321 {
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 322 if (!buffer || !buffer->access || buffer->access->remove_from)
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 323 return -EINVAL;
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 324
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 @325 return buffer->access->remove_from(buffer, data);
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 326 }
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 327 EXPORT_SYMBOL_GPL(iio_buffer_remove_sample);
b4f124803ed8bf Lars-Peter Clausen 2021-08-20 328
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34492 bytes --]
next parent reply other threads:[~2021-08-25 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202108222341.6RtluiRt-lkp@intel.com>
2021-08-25 15:31 ` kernel test robot [this message]
2021-08-20 16:59 [PATCH v4 0/6] iio: Add output buffer support and DAC example Mihail Chindris
2021-08-20 16:59 ` [PATCH v4 1/6] iio: Add output buffer support Mihail Chindris
2021-08-21 0:24 ` kernel test robot
2021-08-23 2:23 ` kernel test robot
2021-08-23 13:50 ` Nuno Sá
2021-08-30 15:42 ` Jonathan Cameron
2021-09-01 8:50 ` Sa, Nuno
2021-09-05 9:54 ` Jonathan Cameron
2021-08-25 8:35 ` Alexandru Ardelean
2021-08-30 16:05 ` Jonathan Cameron
2021-09-01 8:54 ` Sa, Nuno
2021-09-05 9:55 ` Jonathan Cameron
2021-09-16 10:57 ` Chindris, Mihail
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=9837998f-9177-b32f-d71a-e1f1caa2fae2@intel.com \
--to=yujie.liu@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=alexandru.ardelean@analog.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dragos.bogdan@analog.com \
--cc=jic23@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mihail.chindris@analog.com \
--cc=nuno.sa@analog.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