From: kernel test robot <lkp@intel.com>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Gabriele Felici <felicigb@gmail.com>,
Carmine Zaccagnino <carmine@carminezacc.com>
Subject: block/bfq-iosched.c:6171:13: warning: stack frame size (1104) exceeds limit (1024) in 'bfq_insert_requests'
Date: Fri, 14 Jul 2023 03:24:14 +0800 [thread overview]
Message-ID: <202307140331.d3lMVJiF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: eb26cbb1a754ccde5d4d74527dad5ba051808fad
commit: 9778369a2d6c5ed2b81a04164c4aa9da1bdb193d block, bfq: split sync bfq_queues on a per-actuator basis
date: 6 months ago
config: riscv-randconfig-r003-20230713 (https://download.01.org/0day-ci/archive/20230714/202307140331.d3lMVJiF-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project.git f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce: (https://download.01.org/0day-ci/archive/20230714/202307140331.d3lMVJiF-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/202307140331.d3lMVJiF-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> block/bfq-iosched.c:6171:13: warning: stack frame size (1104) exceeds limit (1024) in 'bfq_insert_requests' [-Wframe-larger-than]
static void bfq_insert_requests(struct blk_mq_hw_ctx *hctx,
^
1 warning generated.
vim +/bfq_insert_requests +6171 block/bfq-iosched.c
aee69d78dec0ff Paolo Valente 2017-04-19 6170
aee69d78dec0ff Paolo Valente 2017-04-19 @6171 static void bfq_insert_requests(struct blk_mq_hw_ctx *hctx,
aee69d78dec0ff Paolo Valente 2017-04-19 6172 struct list_head *list, bool at_head)
aee69d78dec0ff Paolo Valente 2017-04-19 6173 {
aee69d78dec0ff Paolo Valente 2017-04-19 6174 while (!list_empty(list)) {
aee69d78dec0ff Paolo Valente 2017-04-19 6175 struct request *rq;
aee69d78dec0ff Paolo Valente 2017-04-19 6176
aee69d78dec0ff Paolo Valente 2017-04-19 6177 rq = list_first_entry(list, struct request, queuelist);
aee69d78dec0ff Paolo Valente 2017-04-19 6178 list_del_init(&rq->queuelist);
aee69d78dec0ff Paolo Valente 2017-04-19 6179 bfq_insert_request(hctx, rq, at_head);
aee69d78dec0ff Paolo Valente 2017-04-19 6180 }
aee69d78dec0ff Paolo Valente 2017-04-19 6181 }
aee69d78dec0ff Paolo Valente 2017-04-19 6182
:::::: The code at line 6171 was first introduced by commit
:::::: aee69d78dec0ffdf82e35d57c626e80dddc314d5 block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler
:::::: TO: Paolo Valente <paolo.valente@linaro.org>
:::::: CC: Jens Axboe <axboe@fb.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-07-13 19:25 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=202307140331.d3lMVJiF-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=carmine@carminezacc.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=felicigb@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=paolo.valente@linaro.org \
/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