lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 23 Jan 2017 18:04:31 +0100 From: Paolo Valente <paolo.valente@...aro.org> To: Jens Axboe <axboe@...com> Cc: Jens Axboe <axboe@...nel.dk>, linux-block@...r.kernel.org, Linux-Kernal <linux-kernel@...r.kernel.org>, Omar Sandoval <osandov@...com>, Linus Walleij <linus.walleij@...aro.org>, Ulf Hansson <ulf.hansson@...aro.org>, Mark Brown <broonie@...nel.org> Subject: Re: [PATCHSET v4] blk-mq-scheduling framework > Il giorno 18 gen 2017, alle ore 17:21, Jens Axboe <axboe@...com> ha scritto: > > On 01/18/2017 08:14 AM, Paolo Valente wrote: >> according to the function blk_mq_sched_put_request, the >> mq.completed_request hook seems to always be invoked (if set) for a >> request for which the mq.put_rq_priv is invoked (if set). > > Correct, any request that came out of blk_mq_sched_get_request() > will always have completed called on it, regardless of whether it > had IO started on it or not. > It seems that some request, after being dispatched, happens to have no mq.put_rq_priv invoked on it now or then. Is it expected? If it is, could you point me to the path through which the end of the life of such a request is handled? Thanks, Paolo > -- > Jens Axboe >
Powered by blists - more mailing lists