mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tomoki Sekiyama <tomoki.sekiyama@hds.com>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	Seiji Aguchi <seiji.aguchi@hds.com>,
	"vgoyal@redhat.com" <vgoyal@redhat.com>,
	"majianpeng@gmail.com" <majianpeng@gmail.com>
Subject: Re: [PATCH v2 1/2] elevator: Fix a race in elevator switching and md device initialization
Date: Mon, 23 Sep 2013 20:11:55 +0000	[thread overview]
Message-ID: <CE661700.7BC5%Tomoki.Sekiyama@hds.com> (raw)
In-Reply-To: <20130922170417.GF30946@htj.dyndns.org>

Hi Tejun,

Thank you for the review.

On 9/22/13 13:04 , "Tejun Heo" <tj@kernel.org> wrote:

>On Fri, Aug 30, 2013 at 06:47:07PM -0400, Tomoki Sekiyama wrote:
>> @@ -739,9 +739,17 @@ blk_init_allocated_queue(struct request_queue *q,
>>request_fn_proc *rfn,
>>  
>>  	q->sg_reserved_size = INT_MAX;
>>  
>> +	/* Protect q->elevator from elevator_change */
>> +	mutex_lock(&q->sysfs_lock);
>> +
>>  	/* init elevator */
>> -	if (elevator_init(q, NULL))
>> +	if (elevator_init(q, NULL)) {
>> +		mutex_unlock(&q->sysfs_lock);
>>  		return NULL;
>> +	}
>> +
>> +	mutex_unlock(&q->sysfs_lock);
>> +
>>  	return q;
>>  }
>>  EXPORT_SYMBOL(blk_init_allocated_queue);
>> diff --git a/block/elevator.c b/block/elevator.c
>> index 668394d..02d4390 100644
>> --- a/block/elevator.c
>> +++ b/block/elevator.c
>> @@ -186,6 +186,12 @@ int elevator_init(struct request_queue *q, char
>>*name)
>>  	struct elevator_type *e = NULL;
>>  	int err;
>>  
>> +	/*
>> +	 * q->sysfs_lock must be held to provide mutual exclusion between
>> +	 * elevator_switch() and here.
>> +	 */
>> +	lockdep_assert_held(&q->sysfs_lock);
>> +
>>  	if (unlikely(q->elevator))
>>  		return 0;
>
>Hmm... why aren't we just changing elevator_init() to grab sysfs_lock
>where necessary?  

The locking cannot be moved into elevator_init() because it is called
from elevator_switch() path, where the request_queue's sysfs_lock is
already taken.

> It'd be more consistent with elevator_exit() that way.

What elevator_exit() locks is elevator_queue's sysfs_lock, not
request_queue's sysfs_lock. What we need here is request_queue's
sysfs_lock.

>Thanks.
>
>-- 
>Tejun


Thanks,
Tomoki Sekiyama



  reply	other threads:[~2013-09-23 20:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30 22:47 Tomoki Sekiyama
2013-08-30 22:47 ` [PATCH v2 2/2] elevator: acquire q->sysfs_lock in elevator_change() Tomoki Sekiyama
2013-09-22 17:00   ` Tejun Heo
2013-09-06 15:01 ` [PATCH v2 1/2] elevator: Fix a race in elevator switching and md device initialization Tomoki Sekiyama
2013-09-22 17:04 ` Tejun Heo
2013-09-23 20:11   ` Tomoki Sekiyama [this message]
2013-09-23 20:14     ` Tejun Heo
2013-10-09 22:36       ` Tomoki Sekiyama

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=CE661700.7BC5%Tomoki.Sekiyama@hds.com \
    --to=tomoki.sekiyama@hds.com \
    --cc=axboe@kernel.dk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=majianpeng@gmail.com \
    --cc=seiji.aguchi@hds.com \
    --cc=tj@kernel.org \
    --cc=vgoyal@redhat.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

all inboxes | Powered by JetHome®