public inbox for linux-bcache@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: zhangshida <starzhangzsd@gmail.com>,
	Johannes.Thumshirn@wdc.com, hch@infradead.org,
	agruenba@redhat.com, ming.lei@redhat.com,
	hsiangkao@linux.alibaba.com, csander@purestorage.com
Cc: oe-kbuild-all@lists.linux.dev, linux-block@vger.kernel.org,
	linux-bcache@vger.kernel.org, nvdimm@lists.linux.dev,
	virtualization@lists.linux.dev, ntfs3@lists.linux.dev,
	linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	zhangshida@kylinos.cn, starzhangzsd@gmail.com
Subject: Re: [PATCH v3 3/9] block: prevent race condition on bi_status in __bio_chain_endio
Date: Sun, 7 Dec 2025 02:01:45 +0800	[thread overview]
Message-ID: <202512070122.my7vkR7A-lkp@intel.com> (raw)
In-Reply-To: <20251129090122.2457896-4-zhangshida@kylinos.cn>

Hi zhangshida,

kernel test robot noticed the following build warnings:

[auto build test WARNING on axboe/for-next]
[also build test WARNING on xfs-linux/for-next nvdimm/libnvdimm-for-next linus/master brauner-vfs/vfs.all v6.18 next-20251205]
[cannot apply to nvdimm/dax-misc]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/zhangshida/md-bcache-fix-improper-use-of-bi_end_io/20251129-170348
base:   https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-next
patch link:    https://lore.kernel.org/r/20251129090122.2457896-4-zhangshida%40kylinos.cn
patch subject: [PATCH v3 3/9] block: prevent race condition on bi_status in __bio_chain_endio
config: loongarch-randconfig-r133-20251130 (https://download.01.org/0day-ci/archive/20251207/202512070122.my7vkR7A-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251207/202512070122.my7vkR7A-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/202512070122.my7vkR7A-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> block/bio.c:319:17: sparse: sparse: cast from restricted blk_status_t
>> block/bio.c:319:17: sparse: sparse: cast from restricted blk_status_t
>> block/bio.c:319:17: sparse: sparse: cast to restricted blk_status_t

vim +319 block/bio.c

   313	
   314	static struct bio *__bio_chain_endio(struct bio *bio)
   315	{
   316		struct bio *parent = bio->bi_private;
   317	
   318		if (bio->bi_status)
 > 319			cmpxchg(&parent->bi_status, 0, bio->bi_status);
   320	
   321		bio_put(bio);
   322		return parent;
   323	}
   324	

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

  parent reply	other threads:[~2025-12-06 18:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-29  9:01 [PATCH v3 0/9] Fix bio chain related issues zhangshida
2025-11-29  9:01 ` [PATCH v3 1/9] md: bcache: fix improper use of bi_end_io zhangshida
2025-12-01  5:45   ` Coly Li
2025-12-01  8:29     ` Stephen Zhang
2025-11-29  9:01 ` [PATCH v3 2/9] block: prohibit calls to bio_chain_endio zhangshida
2025-12-01  6:14   ` Christoph Hellwig
2025-11-29  9:01 ` [PATCH v3 3/9] block: prevent race condition on bi_status in __bio_chain_endio zhangshida
2025-12-01  6:14   ` Christoph Hellwig
2025-12-06 18:01   ` kernel test robot [this message]
2025-11-29  9:01 ` [PATCH v3 4/9] block: export bio_chain_and_submit zhangshida
2025-12-01  6:15   ` Christoph Hellwig
2025-11-29  9:01 ` [PATCH v3 5/9] xfs: Replace the repetitive bio chaining code patterns zhangshida
2025-11-29  9:01 ` [PATCH v3 6/9] block: " zhangshida
2025-11-29  9:01 ` [PATCH v3 7/9] fs/ntfs3: " zhangshida
2025-11-29  9:01 ` [PATCH v3 8/9] zram: " zhangshida
2025-12-04  9:00   ` Sergey Senozhatsky
2025-11-29  9:01 ` [PATCH v3 9/9] nvdimm: " zhangshida

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=202512070122.my7vkR7A-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Johannes.Thumshirn@wdc.com \
    --cc=agruenba@redhat.com \
    --cc=csander@purestorage.com \
    --cc=hch@infradead.org \
    --cc=hsiangkao@linux.alibaba.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=ming.lei@redhat.com \
    --cc=ntfs3@lists.linux.dev \
    --cc=nvdimm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=starzhangzsd@gmail.com \
    --cc=virtualization@lists.linux.dev \
    --cc=zhangshida@kylinos.cn \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox