From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [hch-xfs:xfs-rt-flush-fix 3/3] fs/xfs/xfs_log.c:1562:17: sparse: sparse: cast from restricted blk_status_t
Date: Wed, 02 Sep 2026 08:12:43 +0800 [thread overview]
Message-ID: <202609020822.1RPDKsZq-lkp@intel.com> (raw)
tree: git://git.infradead.org/users/hch/xfs xfs-rt-flush-fix
head: 975adfe299516fcbebccd1db4abc0fe48db8d355
commit: a47cbb38387feb0268f1b79e699dfa16aa1235e7 [3/3] xfs: flush multiple device caches in parallel
config: parisc-randconfig-r132-20260902 (https://download.01.org/0day-ci/archive/20260902/202609020822.1RPDKsZq-lkp@intel.com/config)
compiler: hppa-linux-gcc (GCC) 12.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260902/202609020822.1RPDKsZq-lkp@intel.com/reproduce)
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/202609020822.1RPDKsZq-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> fs/xfs/xfs_log.c:1562:17: sparse: sparse: cast from restricted blk_status_t
>> fs/xfs/xfs_log.c:1562:17: sparse: sparse: cast from restricted blk_status_t
>> fs/xfs/xfs_log.c:1562:17: sparse: sparse: cast to restricted blk_status_t
vim +1562 fs/xfs/xfs_log.c
1554
1555 static void
1556 xlog_flush_end_io(
1557 struct bio *bio)
1558 {
1559 struct xlog_flush_done *done = bio->bi_private;
1560
1561 if (bio->bi_status)
> 1562 cmpxchg(&done->status, 0, bio->bi_status);
1563 xlog_flush_done(done);
1564 bio_put(bio);
1565 }
1566
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-02 0:12 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=202609020822.1RPDKsZq-lkp@intel.com \
--to=lkp@intel.com \
--cc=hch@lst.de \
--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.