From: kernel test robot <lkp@intel.com>
To: Dave Chinner <dchinner@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Chandan Babu R <chandanbabu@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>
Subject: fs/xfs/xfs_linux.h:280 kmem_to_page() warn: unsigned '_x' is never less than zero.
Date: Fri, 14 Feb 2025 10:44:11 +0800 [thread overview]
Message-ID: <202502141023.Rdalsdag-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 68763b29e0a6441f57f9ee652bbf8e7bc59183e5
commit: afdc115559c57a48ad697219cec1d16962ad9e30 xfs: move kmem_to_page()
date: 1 year ago
config: riscv-randconfig-r073-20250213 (https://download.01.org/0day-ci/archive/20250214/202502141023.Rdalsdag-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/202502141023.Rdalsdag-lkp@intel.com/
New smatch warnings:
fs/xfs/xfs_linux.h:280 kmem_to_page() warn: unsigned '_x' is never less than zero.
fs/xfs/xfs_linux.h:280 kmem_to_page() warn: unsigned '_x' is never less than zero.
fs/xfs/xfs_linux.h:280 kmem_to_page() warn: unsigned '_x' is never less than zero.
Old smatch warnings:
fs/xfs/xfs_buf.c:724 xfs_buf_get_map() error: we previously assumed 'bp' could be null (see line 707)
arch/riscv/include/asm/atomic.h:204 arch_atomic_fetch_add_unless() warn: inconsistent indenting
arch/riscv/include/asm/atomic.h:204 arch_atomic_fetch_add_unless() warn: inconsistent indenting
vim +/_x +280 fs/xfs/xfs_linux.h
271
272 /*
273 * Helper for IO routines to grab backing pages from allocated kernel memory.
274 */
275 static inline struct page *
276 kmem_to_page(void *addr)
277 {
278 if (is_vmalloc_addr(addr))
279 return vmalloc_to_page(addr);
> 280 return virt_to_page(addr);
281 }
282
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-02-14 2:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202502141023.Rdalsdag-lkp@intel.com \
--to=lkp@intel.com \
--cc=chandanbabu@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.