From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "jthumshirn@suse.de" <jthumshirn@suse.de>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hare@suse.de" <hare@suse.de>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Subject: Re: [PATCH 04/11] block: Protect queue flag changes with the queue lock
Date: Thu, 1 Mar 2018 15:19:08 +0000 [thread overview]
Message-ID: <1519917546.3204.4.camel@wdc.com> (raw)
In-Reply-To: <20180301085137.6g3hgobf6kj2bosy@linux-x5ow.site>
T24gVGh1LCAyMDE4LTAzLTAxIGF0IDA5OjUxICswMTAwLCBKb2hhbm5lcyBUaHVtc2hpcm4gd3Jv
dGU6DQo+IE9uIFdlZCwgRmViIDI4LCAyMDE4IGF0IDExOjI4OjE2QU0gLTA4MDAsIEJhcnQgVmFu
IEFzc2NoZSB3cm90ZToNCj4gPiAgc3RhdGljIGJvb2wgYmxrX3BvbGxfc3RhdHNfZW5hYmxlKHN0
cnVjdCByZXF1ZXN0X3F1ZXVlICpxKQ0KPiA+ICB7DQo+ID4gLQlpZiAodGVzdF9iaXQoUVVFVUVf
RkxBR19QT0xMX1NUQVRTLCAmcS0+cXVldWVfZmxhZ3MpIHx8DQo+ID4gLQkgICAgdGVzdF9hbmRf
c2V0X2JpdChRVUVVRV9GTEFHX1BPTExfU1RBVFMsICZxLT5xdWV1ZV9mbGFncykpDQo+ID4gKwlp
ZiAoYmxrX3F1ZXVlX2ZsYWdfdGVzdF9hbmRfc2V0KFFVRVVFX0ZMQUdfUE9MTF9TVEFUUywgcSkp
DQo+IA0KPiBJcyB0aGlzIG9uZSByZWFsbHkgbmVlZGVkIG9yIGp1c3QgZm9yIHN5bW1ldHJ5PyBF
dmVuIGlmIHNvbWV0aGluZw0KPiB3b3VsZCBjaGFuZ2UgdGhlIHF1ZXVlX2ZsYWdzIGFmdGVyIHRo
ZSBmaXJzdCB0ZXN0X2JpdCgpIGNhbGwsIHRoZQ0KPiB0ZXN0X2FuZF9zZXRfYml0KCkgd291bGQg
c3RpbGwgZG8gdGhlIHJpZ2h0IHRoaW5nLCB3b3VsZG4ndCBpdD8NCg0KSGVsbG8gSm9oYW5uZXMs
DQoNClNpbmNlIGJsa19wb2xsX3N0YXRzX2VuYWJsZSgpIGlzIGNhbGxlZCBmcm9tIHRoZSBob3Qg
cGF0aCAocG9sbGluZyBjb2RlKSBJDQp0aGluayB3ZSBuZWVkIHRoZSBvcHRpbWl6YXRpb24gb2Yg
Y2FsbGluZyB0ZXN0X2JpdCgpIGJlZm9yZSBjYWxsaW5nDQp0ZXN0X2FuZF9zZXRfYml0KCkuIEkg
d2lsbCByZXN0b3JlIHRoZSB0ZXN0X2JpdCgpIGNhbGwuDQoNCkJhcnQu
next prev parent reply other threads:[~2018-03-01 15:19 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 19:28 [PATCH 00/11] Make all concurrent queue flag manipulations safe Bart Van Assche
2018-02-28 19:28 ` [PATCH 01/11] block: Reorder the queue flag manipulaton function definitions Bart Van Assche
2018-03-01 8:42 ` Johannes Thumshirn
2018-03-02 23:09 ` Martin K. Petersen
2018-03-08 1:02 ` Bart Van Assche
2018-02-28 19:28 ` [PATCH 02/11] block: Use the queue_flag_*() functions instead of open-coding these Bart Van Assche
2018-03-01 8:43 ` Johannes Thumshirn
2018-03-02 23:09 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 03/11] block: Introduce blk_queue_flag_{set,clear,test_and_{set,clear}}() Bart Van Assche
2018-03-01 8:46 ` Johannes Thumshirn
2018-03-02 23:11 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 04/11] block: Protect queue flag changes with the queue lock Bart Van Assche
2018-03-01 8:51 ` Johannes Thumshirn
2018-03-01 15:19 ` Bart Van Assche [this message]
2018-03-01 15:22 ` Johannes Thumshirn
2018-03-02 23:12 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 05/11] mtip32xx: Use the blk_queue_flag_*() functions Bart Van Assche
2018-03-01 8:52 ` Johannes Thumshirn
2018-03-02 23:12 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 06/11] bcache: Use the blk_queue_flag_{set,clear}() functions Bart Van Assche
2018-02-28 20:18 ` Michael Lyle
2018-03-01 8:52 ` Johannes Thumshirn
2018-03-02 23:12 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 07/11] iscsi: Use blk_queue_flag_set() Bart Van Assche
2018-03-01 8:53 ` Johannes Thumshirn
2018-03-02 23:14 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 08/11] target/tcm_loop: " Bart Van Assche
2018-03-01 8:53 ` Johannes Thumshirn
2018-03-02 23:17 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 09/11] block: Use blk_queue_flag_*() in drivers instead of queue_flag_*() Bart Van Assche
2018-03-02 23:17 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 10/11] block: Complain if queue_flag_(set|clear)_unlocked() is abused Bart Van Assche
2018-03-01 8:57 ` Johannes Thumshirn
2018-03-02 23:18 ` Martin K. Petersen
2018-02-28 19:28 ` [PATCH 11/11] block: Move the queue_flag_*() functions from a public into a private header file Bart Van Assche
2018-03-01 8:57 ` Johannes Thumshirn
2018-03-02 23:20 ` Martin K. Petersen
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=1519917546.3204.4.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@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 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.