From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: [hch-xfs:xfs-crc 20/59] fs/xfs/xfs_ioend.c:28 xfs_end_io_read() warn: bitwise AND condition is false here
Date: Sun, 26 Jul 2026 09:41:40 +0800 [thread overview]
Message-ID: <202607260930.j3A7TSNe-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: Christoph Hellwig <hch@lst.de>
tree: git://git.infradead.org/users/hch/xfs xfs-crc
head: 10c7aa6f2c85085eec34737be592d6ae69583782
commit: 5ca814cfff91f77e81966416c9d00673f0f29ebb [20/59] iomap,xfs: move integrity verification to the file system
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: x86_64-randconfig-161-20260725 (https://download.01.org/0day-ci/archive/20260726/202607260930.j3A7TSNe-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9187-g5189e3fb
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202607260930.j3A7TSNe-lkp@intel.com/
New smatch warnings:
fs/xfs/xfs_ioend.c:28 xfs_end_io_read() warn: bitwise AND condition is false here
Old smatch warnings:
fs/xfs/xfs_ioend.c:42 xfs_ioend_submit_read() warn: bitwise AND condition is false here
vim +28 fs/xfs/xfs_ioend.c
8870db508b563d Christoph Hellwig 2026-07-22 20
8870db508b563d Christoph Hellwig 2026-07-22 21 static void
8870db508b563d Christoph Hellwig 2026-07-22 22 xfs_end_io_read(
8870db508b563d Christoph Hellwig 2026-07-22 23 struct bio *bio)
8870db508b563d Christoph Hellwig 2026-07-22 24 {
8870db508b563d Christoph Hellwig 2026-07-22 25 struct iomap_ioend *ioend = iomap_ioend_from_bio(bio);
8870db508b563d Christoph Hellwig 2026-07-22 26 int error = blk_status_to_errno(bio->bi_status);
8870db508b563d Christoph Hellwig 2026-07-22 27
5ca814cfff91f7 Christoph Hellwig 2026-07-22 @28 if (!error && (ioend->io_flags & IOMAP_IOEND_INTEGRITY))
5ca814cfff91f7 Christoph Hellwig 2026-07-22 29 error = iomap_ioend_integrity_verify(ioend);
5ca814cfff91f7 Christoph Hellwig 2026-07-22 30
8870db508b563d Christoph Hellwig 2026-07-22 31 iomap_finish_ioends(ioend, error);
8870db508b563d Christoph Hellwig 2026-07-22 32 }
8870db508b563d Christoph Hellwig 2026-07-22 33
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-26 1:42 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=202607260930.j3A7TSNe-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@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.