From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "joseph.qi@linux.alibaba.com" <joseph.qi@linux.alibaba.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"jack@suse.com" <jack@suse.com>
Subject: Re: [PATCH v3 3/3] block: Fix a race between request queue removal and the block cgroup controller
Date: Thu, 22 Feb 2018 16:59:05 +0000 [thread overview]
Message-ID: <1519318744.2861.3.camel@wdc.com> (raw)
In-Reply-To: <4be27fbf-35a3-034a-f60e-1694393b90e3@linux.alibaba.com>
T24gVGh1LCAyMDE4LTAyLTIyIGF0IDEwOjI1ICswODAwLCBKb3NlcGggUWkgd3JvdGU6DQo+IEkg
bm90aWNlIHRoYXQgc2V2ZXJhbCBkZXZpY2VzIHN1Y2ggYXMgbG9vcCBhbmQgenJhbSB3aWxsIGNh
bGwNCj4gYmxrX2NsZWFudXBfcXVldWUgYmVmb3JlIGRlbF9nZW5kaXNrLCBzbyBpdCB3aWxsIGhp
dCB0aGlzIHdhcm5pbmcuIElzDQo+IHRoaXMgbm9ybWFsPw0KDQpIZWxsbyBKb3NlcGgsDQoNClNp
bmNlIHRoZSBkaXNrIG9iamVjdCBoYXMgYSByZWZlcmVuY2UgdG8gdGhlIHF1ZXVlIEkgYWdyZWUg
d2l0aCBNaW5nIHRoYXQgaXQncw0Kd3JvbmcgdG8gY2FsbCBibGtfY2xlYW51cF9xdWV1ZSgpIGJl
Zm9yZSBkZWxfZ2VuZGlzaygpLiBBbnl3YXksIEkgd2lsbCB2ZXJpZnkNCndoZXRoZXIgdGhlcmUg
YXJlIGFueSBibG9jayBkcml2ZXJzIGluIHdoaWNoIHRoZXNlIGNhbGxzIGhhdmUgdG8gYmUgc3dh
cHBlZC4NCg0KQmFydC4=
next prev parent reply other threads:[~2018-02-22 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 18:44 [PATCH v3 0/3] Fix races between blkcg code and request queue initialization and cleanup Bart Van Assche
2018-02-09 18:44 ` [PATCH v3 1/3] block: Add a third argument to blk_alloc_queue_node() Bart Van Assche
2018-02-09 18:44 ` [PATCH v3 2/3] block: Fix a race between the cgroup code and request queue initialization Bart Van Assche
2018-02-09 18:44 ` [PATCH v3 3/3] block: Fix a race between request queue removal and the block cgroup controller Bart Van Assche
2018-02-22 2:25 ` Joseph Qi
2018-02-22 3:28 ` Ming Lei
2018-02-22 16:59 ` Bart Van Assche [this message]
2018-02-21 22:51 ` [PATCH v3 0/3] Fix races between blkcg code and request queue initialization and cleanup 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=1519318744.2861.3.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=jack@suse.com \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-block@vger.kernel.org \
/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