All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: fs/xfs/xfs_aops.c:665 xfs_zoned_writeback_submit() warn: bitwise AND condition is false here
Date: Fri, 08 May 2026 11:34:08 +0800	[thread overview]
Message-ID: <202605081108.wSTy5QEA-lkp@intel.com> (raw)

BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Christoph Hellwig <hch@lst.de>
CC: Christian Brauner <brauner@kernel.org>
CC: "Darrick J. Wong" <djwong@kernel.org>

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head:   917719c412c48687d4a176965d1fa35320ec457c
commit: 6bbb4d96f797d42d4baef1691a27a62275727146 xfs: support T10 protection information
date:   8 weeks ago
:::::: branch date: 3 hours ago
:::::: commit date: 8 weeks ago
config: i386-randconfig-141-20260508 (https://download.01.org/0day-ci/archive/20260508/202605081108.wSTy5QEA-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
smatch: v0.5.0-9065-ge9cc34fd

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
| Fixes: 6bbb4d96f797 ("xfs: support T10 protection information")
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202605081108.wSTy5QEA-lkp@intel.com/

smatch warnings:
fs/xfs/xfs_aops.c:665 xfs_zoned_writeback_submit() warn: bitwise AND condition is false here

vim +665 fs/xfs/xfs_aops.c

fb7399cf2d0b338 Christoph Hellwig 2025-07-10  651  
058dd70c65ab736 Christoph Hellwig 2025-02-13  652  static int
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  653  xfs_zoned_writeback_submit(
058dd70c65ab736 Christoph Hellwig 2025-02-13  654  	struct iomap_writepage_ctx	*wpc,
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  655  	int				error)
058dd70c65ab736 Christoph Hellwig 2025-02-13  656  {
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  657  	struct iomap_ioend		*ioend = wpc->wb_ctx;
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  658  
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  659  	ioend->io_bio.bi_end_io = xfs_end_bio;
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  660  	if (error) {
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  661  		ioend->io_bio.bi_status = errno_to_blk_status(error);
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  662  		bio_endio(&ioend->io_bio);
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  663  		return error;
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  664  	}
6bbb4d96f797d42 Christoph Hellwig 2026-02-23 @665  	if (wpc->iomap.flags & IOMAP_F_INTEGRITY)
6bbb4d96f797d42 Christoph Hellwig 2026-02-23  666  		fs_bio_integrity_generate(&ioend->io_bio);
f4fa7981fa26c66 Christoph Hellwig 2025-07-10  667  	xfs_zone_alloc_and_submit(ioend, &XFS_ZWPC(wpc)->open_zone);
058dd70c65ab736 Christoph Hellwig 2025-02-13  668  	return 0;
058dd70c65ab736 Christoph Hellwig 2025-02-13  669  }
058dd70c65ab736 Christoph Hellwig 2025-02-13  670  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2026-05-08  3:35 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=202605081108.wSTy5QEA-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.