From: Philip Li <philip.li@intel.com>
To: Baoquan He <bhe@redhat.com>
Cc: kernel test robot <lkp@intel.com>,
<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Yang Li <yang.lee@linux.alibaba.com>
Subject: Re: kernel/vmcore_info.c:117 paddr_vmcoreinfo_note() warn: unsigned '_x' is never less than zero.
Date: Tue, 18 Feb 2025 08:42:03 +0800 [thread overview]
Message-ID: <Z7PXW0NHvgT5eWRu@rli9-mobl> (raw)
In-Reply-To: <Z7Brcjzuh+SG/io1@MiWiFi-R3L-srv>
On Sat, Feb 15, 2025 at 06:24:50PM +0800, Baoquan He wrote:
> On 02/14/25 at 06:44pm, kernel test robot wrote:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head: 128c8f96eb8638c060cd3532dc394d046ce64fe1
> > commit: 443cbaf9e2fdbef7d7cae457434a6cb8a679441b crash: split vmcoreinfo exporting code out from crash_core.c
> > date: 12 months ago
> > config: riscv-randconfig-r073-20250213 (https://download.01.org/0day-ci/archive/20250214/202502141843.5QoKdQ7g-lkp@intel.com/config)
> > compiler: riscv32-linux-gcc (GCC) 14.2.0
> >
> > 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/202502141843.5QoKdQ7g-lkp@intel.com/
> >
> > smatch warnings:
> > kernel/vmcore_info.c:117 paddr_vmcoreinfo_note() warn: unsigned '_x' is never less than zero.
>
> Thanks for reporting this.
>
> I am preparing to reproduce this issue, while I may not know what are
> the steps to reproduce. Just run smatch or just build with the provided
> riscv-randconfig-r073-20250213?
Sorry for late reply, this is from smatch. There're multiple reports similar
to this, and one discussion is at [1], not sure whether this is a false positive.
[1] https://lore.kernel.org/oe-kbuild-all/Z7PWuSA4jtZnxp5J@rli9-mobl/T/#t
>
> >
> > vim +/_x +117 kernel/vmcore_info.c
> >
> > 114
> > 115 phys_addr_t __weak paddr_vmcoreinfo_note(void)
> > 116 {
> > > 117 return __pa(vmcoreinfo_note);
> > 118 }
> > 119 EXPORT_SYMBOL(paddr_vmcoreinfo_note);
> > 120
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
> >
>
>
prev parent reply other threads:[~2025-02-18 0:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-14 10:44 kernel test robot
2025-02-15 10:24 ` Baoquan He
2025-02-18 0:42 ` Philip Li [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=Z7PXW0NHvgT5eWRu@rli9-mobl \
--to=philip.li@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yang.lee@linux.alibaba.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