All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Christoph Hellwig <hch@infradead.org>,
	Hannes Reinecke <hare@suse.com>,
	Johannes Thumshirn <jth@kernel.org>,
	syzbot+d44e1b26ce5c3e77458d@syzkaller.appspotmail.com
Subject: Re: [PATCH v3 2/8] blk-mq: Keep set->nr_hw_queues and set->map[].nr_queues in sync
Date: Fri, 6 Mar 2020 10:46:24 +0800	[thread overview]
Message-ID: <20200306024624.GC4552@ming.t460p> (raw)
In-Reply-To: <20200225004727.GA27445@ming.t460p>

On Tue, Feb 25, 2020 at 08:47:27AM +0800, Ming Lei wrote:
> On Thu, Feb 20, 2020 at 07:22:37PM -0800, Bart Van Assche wrote:
> > blk_mq_map_queues() and multiple .map_queues() implementations expect that
> > set->map[HCTX_TYPE_DEFAULT].nr_queues is set to the number of hardware
> > queues. Hence set .nr_queues before calling these functions. This patch
> > fixes the following kernel warning:
> > 
> > WARNING: CPU: 0 PID: 2501 at include/linux/cpumask.h:137
> > Call Trace:
> >  blk_mq_run_hw_queue+0x19d/0x350 block/blk-mq.c:1508
> >  blk_mq_run_hw_queues+0x112/0x1a0 block/blk-mq.c:1525
> >  blk_mq_requeue_work+0x502/0x780 block/blk-mq.c:775
> >  process_one_work+0x9af/0x1740 kernel/workqueue.c:2269
> >  worker_thread+0x98/0xe40 kernel/workqueue.c:2415
> >  kthread+0x361/0x430 kernel/kthread.c:255
> > 
> > Cc: Christoph Hellwig <hch@infradead.org>
> > Cc: Ming Lei <ming.lei@redhat.com>
> > Cc: Hannes Reinecke <hare@suse.com>
> > Cc: Johannes Thumshirn <jth@kernel.org>
> > Reported-by: syzbot+d44e1b26ce5c3e77458d@syzkaller.appspotmail.com
> > Fixes: ed76e329d74a ("blk-mq: abstract out queue map") # v5.0
> > Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> > ---
> >  block/blk-mq.c | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/block/blk-mq.c b/block/blk-mq.c
> > index f298500e6dda..a92444c077bc 100644
> > --- a/block/blk-mq.c
> > +++ b/block/blk-mq.c
> > @@ -3023,6 +3023,14 @@ static int blk_mq_alloc_rq_maps(struct blk_mq_tag_set *set)
> >  
> >  static int blk_mq_update_queue_map(struct blk_mq_tag_set *set)
> >  {
> > +	/*
> > +	 * blk_mq_map_queues() and multiple .map_queues() implementations
> > +	 * expect that set->map[HCTX_TYPE_DEFAULT].nr_queues is set to the
> > +	 * number of hardware queues.
> > +	 */
> > +	if (set->nr_maps == 1)
> > +		set->map[HCTX_TYPE_DEFAULT].nr_queues = set->nr_hw_queues;
> > +
> >  	if (set->ops->map_queues && !is_kdump_kernel()) {
> >  		int i;
> >  
> > 
> 
> Reviewed-by: Ming Lei <ming.lei@redhat.com>
> 

Hi Jens,

This one and the 3rd patch may belong to 5.6, any chance to consider
them to 5.6?


Thanks,
Ming


  reply	other threads:[~2020-03-06  2:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-21  3:22 [PATCH v3 0/8] Improve changing the number of hardware queues Bart Van Assche
2020-02-21  3:22 ` [PATCH v3 1/8] blk-mq: Fix a comment in include/linux/blk-mq.h Bart Van Assche
2020-02-24 10:58   ` Chaitanya Kulkarni
2020-02-21  3:22 ` [PATCH v3 2/8] blk-mq: Keep set->nr_hw_queues and set->map[].nr_queues in sync Bart Van Assche
2020-02-24 11:00   ` Chaitanya Kulkarni
2020-02-25  0:47   ` Ming Lei
2020-03-06  2:46     ` Ming Lei [this message]
2020-03-06 10:04       ` Ming Lei
2020-02-21  3:22 ` [PATCH v3 3/8] blk-mq: Fix a recently introduced regression in blk_mq_realloc_hw_ctxs() Bart Van Assche
2020-02-21  3:22 ` [PATCH v3 4/8] null_blk: Suppress an UBSAN complaint triggered when setting 'memory_backed' Bart Van Assche
2020-02-24 11:28   ` Chaitanya Kulkarni
2020-02-24 15:20     ` Bart Van Assche
2020-02-21  3:22 ` [PATCH v3 5/8] null_blk: Fix changing the number of hardware queues Bart Van Assche
2020-02-21  3:22 ` [PATCH v3 6/8] null_blk: Fix the null_add_dev() error path Bart Van Assche
2020-02-24 11:30   ` Chaitanya Kulkarni
2020-02-21  3:22 ` [PATCH v3 7/8] null_blk: Handle null_add_dev() failures properly Bart Van Assche
2020-02-24 11:31   ` Chaitanya Kulkarni
2020-02-21  3:22 ` [PATCH v3 8/8] null_blk: Add support for init_hctx() fault injection Bart Van Assche

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=20200306024624.GC4552@ming.t460p \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=hare@suse.com \
    --cc=hch@infradead.org \
    --cc=hch@lst.de \
    --cc=jth@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=syzbot+d44e1b26ce5c3e77458d@syzkaller.appspotmail.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 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.