public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Hui Su <sh_def@163.com>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block/elevator: reduce the critical section
Date: Mon, 19 Oct 2020 11:23:48 -0600	[thread overview]
Message-ID: <ea4495c3-0003-786d-82e4-3693f349890a@kernel.dk> (raw)
In-Reply-To: <20201019164246.GA79115@rlk>

On 10/19/20 10:42 AM, Hui Su wrote:
> @@ -633,23 +633,21 @@ static struct elevator_type *elevator_get_default(struct request_queue *q)
>   */
>  static struct elevator_type *elevator_get_by_features(struct request_queue *q)
>  {
> -	struct elevator_type *e, *found = NULL;
> +	struct elevator_type *e = NULL;
>  
>  	spin_lock(&elv_list_lock);
> -
>  	list_for_each_entry(e, &elv_list, list) {
>  		if (elv_support_features(e->elevator_features,
>  					 q->required_elevator_features)) {
> -			found = e;
>  			break;
>  		}
>  	}
> +	spin_unlock(&elv_list_lock);
>  
> -	if (found && !try_module_get(found->elevator_owner))
> -		found = NULL;
> +	if (e && !try_module_get(e->elevator_owner))
> +		e = NULL;
>  
> -	spin_unlock(&elv_list_lock);
> -	return found;
> +	return e;
>  }

This looks wrong as well. If we don't match the elevator, then we just
return the last one. Or maybe even a totally invalid entry, depending on
how the list iteration works.


-- 
Jens Axboe


      parent reply	other threads:[~2020-10-19 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-19 16:42 [PATCH] block/elevator: reduce the critical section Hui Su
2020-10-19 16:50 ` Jens Axboe
2020-10-19 17:23 ` Jens Axboe [this message]

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=ea4495c3-0003-786d-82e4-3693f349890a@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sh_def@163.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