From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: Re: [PATCH 14/14] block: Enable lock context analysis for all block drivers
Date: Fri, 6 Mar 2026 16:02:12 +0800 [thread overview]
Message-ID: <202603061658.H8q89fcs-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "only suspicious fbc files changed"
::::::
BCC: lkp@intel.com
CC: llvm@lists.linux.dev
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20260304194843.760669-15-bvanassche@acm.org>
References: <20260304194843.760669-15-bvanassche@acm.org>
TO: Bart Van Assche <bvanassche@acm.org>
TO: Jens Axboe <axboe@kernel.dk>
CC: Christoph Hellwig <hch@lst.de>
CC: Damien Le Moal <dlemoal@kernel.org>
CC: Marco Elver <elver@google.com>
CC: linux-block@vger.kernel.org
CC: Bart Van Assche <bvanassche@acm.org>
CC: Justin Sanders <justin@coraid.com>
CC: Philipp Reisner <philipp.reisner@linbit.com>
CC: Lars Ellenberg <lars.ellenberg@linbit.com>
CC: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
CC: "Md. Haris Iqbal" <haris.iqbal@ionos.com>
CC: Jack Wang <jinpu.wang@ionos.com>
CC: "Roger Pau Monné" <roger.pau@citrix.com>
CC: Minchan Kim <minchan@kernel.org>
CC: Sergey Senozhatsky <senozhatsky@chromium.org>
Hi Bart,
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe/for-next]
[also build test WARNING on bpf-next/net bpf-next/master bpf/master linus/master v7.0-rc2 next-20260305]
[cannot apply to ceph-client/testing ceph-client/for-linus hch-configfs/for-next]
[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/Bart-Van-Assche/drbd-Balance-RCU-calls-in-drbd_adm_dump_devices/20260305-035510
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-next
patch link: https://lore.kernel.org/r/20260304194843.760669-15-bvanassche%40acm.org
patch subject: [PATCH 14/14] block: Enable lock context analysis for all block drivers
:::::: branch date: 2 days ago
:::::: commit date: 2 days ago
config: sparc64-allmodconfig (https://download.01.org/0day-ci/archive/20260306/202603061658.H8q89fcs-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project c32caeec8158d634bb71ab8911a6031248b9fc47)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260306/202603061658.H8q89fcs-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/r/202603061658.H8q89fcs-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/block/sunvdc.c:1124:2: warning: releasing spinlock 'port->vio.lock' that was not held [-Wthread-safety-analysis]
1124 | spin_unlock_irq(&port->vio.lock);
| ^
>> drivers/block/sunvdc.c:1133:1: warning: spinlock 'port->vio.lock' is still held at the end of function [-Wthread-safety-analysis]
1133 | }
| ^
drivers/block/sunvdc.c:1129:2: note: spinlock acquired here
1129 | spin_lock_irq(&port->vio.lock);
| ^
2 warnings generated.
vim +1124 drivers/block/sunvdc.c
76e74bbe0a38c67 Dwight Engen 2014-12-11 1113
76e74bbe0a38c67 Dwight Engen 2014-12-11 1114 static void vdc_queue_drain(struct vdc_port *port)
76e74bbe0a38c67 Dwight Engen 2014-12-11 1115 {
fa182a1fa97dff5 Jens Axboe 2018-10-15 1116 struct request_queue *q = port->disk->queue;
1e1a9cecfab3f22 Christoph Hellwig 2025-01-31 1117 unsigned int memflags;
fa182a1fa97dff5 Jens Axboe 2018-10-15 1118
fa182a1fa97dff5 Jens Axboe 2018-10-15 1119 /*
fa182a1fa97dff5 Jens Axboe 2018-10-15 1120 * Mark the queue as draining, then freeze/quiesce to ensure
fa182a1fa97dff5 Jens Axboe 2018-10-15 1121 * that all existing requests are seen in ->queue_rq() and killed
fa182a1fa97dff5 Jens Axboe 2018-10-15 1122 */
fa182a1fa97dff5 Jens Axboe 2018-10-15 1123 port->drain = 1;
fa182a1fa97dff5 Jens Axboe 2018-10-15 @1124 spin_unlock_irq(&port->vio.lock);
76e74bbe0a38c67 Dwight Engen 2014-12-11 1125
1e1a9cecfab3f22 Christoph Hellwig 2025-01-31 1126 memflags = blk_mq_freeze_queue(q);
fa182a1fa97dff5 Jens Axboe 2018-10-15 1127 blk_mq_quiesce_queue(q);
fa182a1fa97dff5 Jens Axboe 2018-10-15 1128
fa182a1fa97dff5 Jens Axboe 2018-10-15 1129 spin_lock_irq(&port->vio.lock);
fa182a1fa97dff5 Jens Axboe 2018-10-15 1130 port->drain = 0;
64b48ec36dbed56 Stephen Rothwell 2025-02-03 1131 blk_mq_unquiesce_queue(q);
64b48ec36dbed56 Stephen Rothwell 2025-02-03 1132 blk_mq_unfreeze_queue(q, memflags);
76e74bbe0a38c67 Dwight Engen 2014-12-11 @1133 }
76e74bbe0a38c67 Dwight Engen 2014-12-11 1134
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-03-06 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-06 8:02 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-04 19:48 [PATCH 00/14] Enable lock context analysis Bart Van Assche
2026-03-04 19:48 ` [PATCH 14/14] block: Enable lock context analysis for all block drivers Bart Van Assche
2026-03-05 1:33 ` Sergey Senozhatsky
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=202603061658.H8q89fcs-lkp@intel.com \
--to=lkp@intel.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.