From: Justin He <Justin.He@arm.com>
To: kernel test robot <lkp@intel.com>
Cc: "oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, nd <nd@arm.com>
Subject: RE: ERROR: modpost: vmlinux: local symbol 'dma_addressing_limited' was exported
Date: Wed, 6 Dec 2023 13:03:03 +0000 [thread overview]
Message-ID: <DBBPR08MB45389EB25B0C89853366E5D2F784A@DBBPR08MB4538.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <202312061307.TwC5Kt2r-lkp@intel.com>
> -----Original Message-----
> From: kernel test robot <lkp@intel.com>
> Sent: Wednesday, December 6, 2023 1:15 PM
> To: Justin He <Justin.He@arm.com>
> Cc: oe-kbuild-all@lists.linux.dev; linux-kernel@vger.kernel.org; Christoph
> Hellwig <hch@lst.de>
> Subject: ERROR: modpost: vmlinux: local symbol 'dma_addressing_limited'
> was exported
[...]
> ERROR: modpost: vmlinux: local symbol 'dma_sync_single_for_device' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_sync_sg_for_cpu' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_sync_sg_for_device' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_get_sgtable_attrs' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_can_mmap' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_mmap_attrs' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_get_required_mask' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_alloc_attrs' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_free_attrs' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_alloc_pages' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_free_pages' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_mmap_pages' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_alloc_noncontiguous' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_free_noncontiguous' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_vmap_noncontiguous' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_vunmap_noncontiguous' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_mmap_noncontiguous' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_pci_p2pdma_supported' was
> exported
> ERROR: modpost: vmlinux: local symbol 'dma_set_mask' was exported
> ERROR: modpost: vmlinux: local symbol 'dma_set_coherent_mask' was
> exported
> >> ERROR: modpost: vmlinux: local symbol 'dma_addressing_limited' was
> >> exported
Since the dma_set_mask/ dma_set_coherent_mask was also in the error list, can I
consider it as a false positive warning?
Besides, I followed the reproducing instructions and got:
# nm build_dir/vmlinux |grep dma_addressing_limited
ffffffff81b2a974 r __crc_dma_addressing_limited
ffffffff8008ac36 T dma_addressing_limited
ffffffff81b330b5 r __kstrtab_dma_addressing_limited
ffffffff81b4e5f2 r __kstrtabns_dma_addressing_limited
ffffffff81b0aec0 r __ksymtab_dma_addressing_limited
Seems dma_addressing_limited is not a local symbol, is it?
--
Cheers,
Justin (Jia He)
prev parent reply other threads:[~2023-12-06 13:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 5:15 kernel test robot
2023-12-06 13:03 ` Justin He [this message]
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=DBBPR08MB45389EB25B0C89853366E5D2F784A@DBBPR08MB4538.eurprd08.prod.outlook.com \
--to=justin.he@arm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=nd@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®