From: kernel test robot <lkp@intel.com>
To: Yu Kuai <yukuai@fnnas.com>,
axboe@kernel.dk, linux-block@vger.kernel.org, tj@kernel.org,
nilay@linux.ibm.com, ming.lei@redhat.com, bvanassche@acm.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev, yukuai@fnnas.com
Subject: Re: [PATCH v2 4/9] blk-mq-debugfs: warn about possible deadlock
Date: Sat, 22 Nov 2025 10:50:55 +0800 [thread overview]
Message-ID: <202511221056.dAY0duWw-lkp@intel.com> (raw)
In-Reply-To: <20251121062829.1433332-5-yukuai@fnnas.com>
Hi Yu,
kernel test robot noticed the following build errors:
[auto build test ERROR on axboe/for-next]
[also build test ERROR on linus/master v6.18-rc6 next-20251121]
[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/Yu-Kuai/blk-mq-debugfs-factor-out-a-helper-to-register-debugfs-for-all-rq_qos/20251121-143315
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git for-next
patch link: https://lore.kernel.org/r/20251121062829.1433332-5-yukuai%40fnnas.com
patch subject: [PATCH v2 4/9] blk-mq-debugfs: warn about possible deadlock
config: sparc64-defconfig (https://download.01.org/0day-ci/archive/20251122/202511221056.dAY0duWw-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251122/202511221056.dAY0duWw-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/202511221056.dAY0duWw-lkp@intel.com/
All errors (new ones prefixed by >>):
>> block/blk-mq-debugfs.c:628:30: error: no member named 'blkcg_mutex' in 'struct request_queue'
628 | lockdep_assert_not_held(&q->blkcg_mutex);
| ~ ^
include/linux/lockdep.h:393:49: note: expanded from macro 'lockdep_assert_not_held'
393 | #define lockdep_assert_not_held(l) do { (void)(l); } while (0)
| ^
1 error generated.
vim +628 block/blk-mq-debugfs.c
612
613 static void debugfs_create_files(struct request_queue *q, struct dentry *parent,
614 void *data,
615 const struct blk_mq_debugfs_attr *attr)
616 {
617 /*
618 * Creating new debugfs entries with queue freezed has the risk of
619 * deadlock.
620 */
621 WARN_ON_ONCE(q->mq_freeze_depth != 0);
622 /*
623 * debugfs_mutex should not be nested under other locks that can be
624 * grabbed while queue is frozen.
625 */
626 lockdep_assert_not_held(&q->elevator_lock);
627 lockdep_assert_not_held(&q->rq_qos_mutex);
> 628 lockdep_assert_not_held(&q->blkcg_mutex);
629
630 if (IS_ERR_OR_NULL(parent))
631 return;
632
633 for (; attr->name; attr++)
634 debugfs_create_file_aux(attr->name, attr->mode, parent,
635 (void *)attr, data, &blk_mq_debugfs_fops);
636 }
637
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2025-11-22 2:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251121062829.1433332-5-yukuai@fnnas.com>
2025-11-22 2:50 ` kernel test robot [this message]
2025-11-22 16:04 ` [PATCH v2 4/9] blk-mq-debugfs: warn about possible deadlock Yu Kuai
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=202511221056.dAY0duWw-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=linux-block@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ming.lei@redhat.com \
--cc=nilay@linux.ibm.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=tj@kernel.org \
--cc=yukuai@fnnas.com \
/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;
as well as URLs for NNTP newsgroup(s).