From: kernel test robot <lkp@intel.com>
To: Dongsheng Yang <dongsheng.yang@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev, Mikulas Patocka <mpatocka@redhat.com>
Subject: [linux-next:master 2532/2770] drivers/md/dm-pcache/backing_dev.c:134:26: sparse: sparse: incorrect type in assignment (different base types)
Date: Sat, 16 Aug 2025 18:52:36 +0800 [thread overview]
Message-ID: <202508161838.BV3mincB-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 1357b2649c026b51353c84ddd32bc963e8999603
commit: 6fb8fbbaf147fe4153177320ee354c457605800a [2532/2770] dm-pcache: add persistent cache target in device-mapper
config: riscv-randconfig-r132-20250816 (https://download.01.org/0day-ci/archive/20250816/202508161838.BV3mincB-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 93d24b6b7b148c47a2fa228a4ef31524fa1d9f3f)
reproduce: (https://download.01.org/0day-ci/archive/20250816/202508161838.BV3mincB-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/202508161838.BV3mincB-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
WARNING: invalid argument to '-march': '_zacas_zabha'
>> drivers/md/dm-pcache/backing_dev.c:134:26: sparse: sparse: incorrect type in assignment (different base types) @@ expected int ret @@ got restricted blk_status_t [usertype] bi_status @@
drivers/md/dm-pcache/backing_dev.c:134:26: sparse: expected int ret
drivers/md/dm-pcache/backing_dev.c:134:26: sparse: got restricted blk_status_t [usertype] bi_status
vim +134 drivers/md/dm-pcache/backing_dev.c
127
128 static void backing_dev_bio_end(struct bio *bio)
129 {
130 struct pcache_backing_dev_req *backing_req = bio->bi_private;
131 struct pcache_backing_dev *backing_dev = backing_req->backing_dev;
132 unsigned long flags;
133
> 134 backing_req->ret = bio->bi_status;
135
136 spin_lock_irqsave(&backing_dev->complete_lock, flags);
137 list_move_tail(&backing_req->node, &backing_dev->complete_list);
138 queue_work(BACKING_DEV_TO_PCACHE(backing_dev)->task_wq, &backing_dev->req_complete_work);
139 spin_unlock_irqrestore(&backing_dev->complete_lock, flags);
140 }
141
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-16 10:52 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=202508161838.BV3mincB-lkp@intel.com \
--to=lkp@intel.com \
--cc=dongsheng.yang@linux.dev \
--cc=mpatocka@redhat.com \
--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.