All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Vincent Fu <vincent.fu@samsung.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] null_blk: cleanup null_init_tag_set
Date: Fri, 15 Jul 2022 22:30:04 +0800	[thread overview]
Message-ID: <YtF57BoFppNm19wf@T590> (raw)
In-Reply-To: <c109ba5ec91c4fffb1ae834d50076dda@samsung.com>

On Fri, Jul 15, 2022 at 02:11:21PM +0000, Vincent Fu wrote:
> > -----Original Message-----
> > From: Ming Lei [mailto:ming.lei@redhat.com]
> > Sent: Thursday, July 14, 2022 11:19 PM
> > To: Jens Axboe <axboe@kernel.dk>
> > Cc: linux-block@vger.kernel.org; Ming Lei <ming.lei@redhat.com>;
> > Vincent Fu <vincent.fu@samsung.com>
> > Subject: [PATCH] null_blk: cleanup null_init_tag_set
> > 
> > The passed 'nullb' can be NULL, so cause null ptr reference.
> > 
> > Fix the issue, meantime cleanup null_init_tag_set for avoiding to add
> > similar issue in future.
> > 
> > Cc: Vincent Fu <vincent.fu@samsung.com>
> > Fixes: 37ae152c7a0d ("null_blk: add configfs variables for 2 options")
> > Signed-off-by: Ming Lei <ming.lei@redhat.com>
> > ---
> >  drivers/block/null_blk/main.c | 49 ++++++++++++++++++++++-----------
> > --
> >  1 file changed, 31 insertions(+), 18 deletions(-)
> > 
> > diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
> > index c955a07dba2d..a08856b121b3 100644
> > --- a/drivers/block/null_blk/main.c
> > +++ b/drivers/block/null_blk/main.c
> > @@ -1898,31 +1898,44 @@ static int null_gendisk_register(struct nullb
> > *nullb)
> > 
> >  static int null_init_tag_set(struct nullb *nullb, struct blk_mq_tag_set
> > *set)
> >  {
> > +	unsigned int flags = BLK_MQ_F_SHOULD_MERGE;
> > +	int hw_queues, numa_node;
> > +	unsigned int queue_depth;
> >  	int poll_queues;
> > 
> > +	if (nullb) {
> > +		hw_queues = nullb->dev->submit_queues;
> > +		poll_queues = nullb->dev->poll_queues;
> > +		queue_depth = nullb->dev->hw_queue_depth;
> > +		numa_node = nullb->dev->home_node;
> > +		if (nullb->dev->no_sched)
> > +			flags |= BLK_MQ_F_NO_SCHED;
> > +		if (nullb->dev->shared_tag_bitmap)
> > +			flags |= BLK_MQ_F_TAG_HCTX_SHARED;
> > +		if (nullb->dev->blocking)
> > +			flags |= BLK_MQ_F_BLOCKING;
> > +	} else {
> > +		hw_queues = g_submit_queues;
> > +		poll_queues = g_poll_queues;
> > +		queue_depth = g_hw_queue_depth;
> > +		numa_node = g_home_node;
> > +		if (g_blocking)
> > +			flags |= BLK_MQ_F_BLOCKING;
> > +	}
> > +
> 
> Ming, thank you for fixing the mess I created.
> 
> I believe that even when 'nullb' is NULL we should still set the
> BLK_MQ_F_NO_SCHED and BLK_MQ_F_TAG_HCTX_SHARED flags based on the values of
> g_no_sched and g_shared_tag_bitmap, respectively. Is that not right?

Yeah, it is right, and I have covered it in V2.

Thanks,
Ming


  reply	other threads:[~2022-07-15 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20220715031940uscas1p27e74dec9ebf60d454441271aabe147de@uscas1p2.samsung.com>
2022-07-15  3:19 ` [PATCH] null_blk: cleanup null_init_tag_set Ming Lei
2022-07-15 14:11   ` Vincent Fu
2022-07-15 14:30     ` Ming Lei [this message]
2022-07-15 13:19 Sachin Sant

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=YtF57BoFppNm19wf@T590 \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=vincent.fu@samsung.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.