From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "hch@infradead.org" <hch@infradead.org>,
"ming.lei@redhat.com" <ming.lei@redhat.com>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"paolo.valente@linaro.org" <paolo.valente@linaro.org>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>,
"osandov@fb.com" <osandov@fb.com>,
"holger@applied-asynchrony.com" <holger@applied-asynchrony.com>
Subject: Re: [PATCH 2/2] block: kyber: fix domain token leak during requeue
Date: Fri, 23 Feb 2018 17:12:39 +0000 [thread overview]
Message-ID: <1519405958.2904.23.camel@wdc.com> (raw)
In-Reply-To: <20180223153657.17376-3-ming.lei@redhat.com>
T24gRnJpLCAyMDE4LTAyLTIzIGF0IDIzOjM2ICswODAwLCBNaW5nIExlaSB3cm90ZToNCj4gV2hl
biByZXF1ZXVpbmcgcmVxdWVzdCwgdGhlIGRvbWFpbiB0b2tlbiBzaG91bGQgaGF2ZSBiZWVuIGZy
ZWVkDQo+IGJlZm9yZSByZS1pbnNlcnRpbmcgdGhlIHJlcXVlc3QgdG8gaW8gc2NoZWR1bGVyLiBP
dGhlcndpc2UsIHRoZQ0KPiBhc3NpZ25lZCBkb21haW4gdG9rZW4gd2lsbCBiZSBsZWFrZWQsIGFu
ZCBJTyBoYW5nIGNhbiBiZSBjYXVzZWQuDQoNClBsZWFzZSBjb25zaWRlciB0byBhZGQgYSAiQ2M6
IHN0YWJsZSIgdGFnIHRvIHRoaXMgcGF0Y2guDQoNCkFueXdheToNCg0KUmV2aWV3ZWQtYnk6IEJh
cnQgVmFuIEFzc2NoZSA8YmFydC52YW5hc3NjaGVAd2RjLmNvbT4NCg0KDQo=
next prev parent reply other threads:[~2018-02-23 17:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-23 15:36 [PATCH 0/2] blk-mq: kyber: fix domain token leak during requeue Ming Lei
2018-02-23 15:36 ` [PATCH 1/2] blk-mq: don't call io sched's .requeue_request when requeueing rq to ->dispatch Ming Lei
2018-02-24 1:08 ` Bart Van Assche
2018-02-24 16:17 ` Paolo Valente
2018-02-23 15:36 ` [PATCH 2/2] block: kyber: fix domain token leak during requeue Ming Lei
2018-02-23 17:12 ` Bart Van Assche [this message]
2018-02-24 22:56 ` [PATCH 0/2] blk-mq: " Jens Axboe
2018-02-26 23:41 ` Omar Sandoval
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=1519405958.2904.23.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=holger@applied-asynchrony.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=oleksandr@natalenko.name \
--cc=osandov@fb.com \
--cc=paolo.valente@linaro.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;
as well as URLs for NNTP newsgroup(s).