From: Leon Romanovsky <leon@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Marek Szyprowski <m.szyprowski@samsung.com>,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [linux-next:master 7677/9696] mm/kmsan/hooks.c:372:6: error: too many arguments to function call, expected 3, have 4
Date: Wed, 17 Sep 2025 09:19:05 +0300 [thread overview]
Message-ID: <20250917061905.GA6464@unreal> (raw)
In-Reply-To: <202509170638.AMGNCMEE-lkp@intel.com>
On Wed, Sep 17, 2025 at 06:15:12AM +0800, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 05af764719214d6568adb55c8749dec295228da8
> commit: 6eb1e769b2c13a33cb2ca694454a7561d3d72c0a [7677/9696] kmsan: convert kmsan_handle_dma to use physical addresses
I think that it is old report.
The commit in the DMA tree has different SHA and correct kmsan_handle_dma() callers:
b420b31f009f ("kmsan: convert kmsan_handle_dma to use physical addresses")
Thanks
> config: x86_64-buildonly-randconfig-002-20250917 (https://download.01.org/0day-ci/archive/20250917/202509170638.AMGNCMEE-lkp@intel.com/config)
> compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250917/202509170638.AMGNCMEE-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/202509170638.AMGNCMEE-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
> >> mm/kmsan/hooks.c:372:6: error: too many arguments to function call, expected 3, have 4
> 371 | kmsan_handle_dma(sg_page(item), item->offset, item->length,
> | ~~~~~~~~~~~~~~~~
> 372 | dir);
> | ^~~
> mm/kmsan/hooks.c:362:19: note: 'kmsan_handle_dma' declared here
> 362 | EXPORT_SYMBOL_GPL(kmsan_handle_dma);
> | ^~~~~~~~~~~~~~~~
> include/linux/export.h:90:48: note: expanded from macro 'EXPORT_SYMBOL_GPL'
> 90 | #define EXPORT_SYMBOL_GPL(sym) _EXPORT_SYMBOL(sym, "GPL")
> | ^~~
> include/linux/export.h:86:54: note: expanded from macro '_EXPORT_SYMBOL'
> 86 | #define _EXPORT_SYMBOL(sym, license) __EXPORT_SYMBOL(sym, license, "")
> | ^~~
> include/linux/export.h:76:21: note: expanded from macro '__EXPORT_SYMBOL'
> 76 | extern typeof(sym) sym; \
> | ^~~
> 1 error generated.
>
>
> vim +372 mm/kmsan/hooks.c
>
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 363
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 364 void kmsan_handle_dma_sg(struct scatterlist *sg, int nents,
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 365 enum dma_data_direction dir)
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 366 {
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 367 struct scatterlist *item;
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 368 int i;
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 369
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 370 for_each_sg(sg, item, nents, i)
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 371 kmsan_handle_dma(sg_page(item), item->offset, item->length,
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 @372 dir);
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 373 }
> 7ade4f10779cb4 Alexander Potapenko 2022-09-15 374
>
> :::::: The code at line 372 was first introduced by commit
> :::::: 7ade4f10779cb46f5c29ced9b7a41f68501cf0ed dma: kmsan: unpoison DMA mappings
>
> :::::: TO: Alexander Potapenko <glider@google.com>
> :::::: CC: Andrew Morton <akpm@linux-foundation.org>
>
> --
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-09-17 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 22:15 [linux-next:master 7677/9696] mm/kmsan/hooks.c:372:6: error: too many arguments to function call, expected 3, have 4 kernel test robot
2025-09-17 6:19 ` Leon Romanovsky [this message]
2025-09-17 6:27 ` Leon Romanovsky
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=20250917061905.GA6464@unreal \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=m.szyprowski@samsung.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 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.