From: Mike Snitzer <snitzer@redhat.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
"James E . J . Bottomley" <jejb@linux.ibm.com>,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, "Ewan D . Milne" <emilne@redhat.com>,
Bart Van Assche <bvanassche@acm.org>,
Hannes Reinecke <hare@suse.com>, Christoph Hellwig <hch@lst.de>,
dm-devel@redhat.com, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] blk-mq: add callback of .cleanup_rq
Date: Thu, 18 Jul 2019 10:52:01 -0400 [thread overview]
Message-ID: <20190718145201.GA2305@redhat.com> (raw)
In-Reply-To: <20190718032519.28306-2-ming.lei@redhat.com>
On Wed, Jul 17 2019 at 11:25pm -0400,
Ming Lei <ming.lei@redhat.com> wrote:
> dm-rq needs to free request which has been dispatched and not completed
> by underlying queue. However, the underlying queue may have allocated
> private stuff for this request in .queue_rq(), so dm-rq will leak the
> request private part.
No, SCSI (and blk-mq) will leak. DM doesn't know anything about the
internal memory SCSI uses. That memory is a SCSI implementation detail.
Please fix header to properly reflect which layer is doing the leaking.
> Add one new callback of .cleanup_rq() to fix the memory leak issue.
>
> Another use case is to free request when the hctx is dead during
> cpu hotplug context.
>
> Cc: Ewan D. Milne <emilne@redhat.com>
> Cc: Bart Van Assche <bvanassche@acm.org>
> Cc: Hannes Reinecke <hare@suse.com>
> Cc: Christoph Hellwig <hch@lst.de>
> Cc: Mike Snitzer <snitzer@redhat.com>
> Cc: dm-devel@redhat.com
> Cc: <stable@vger.kernel.org>
> Fixes: 396eaf21ee17 ("blk-mq: improve DM's blk-mq IO merging via blk_insert_cloned_request feedback")
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> drivers/md/dm-rq.c | 1 +
> include/linux/blk-mq.h | 13 +++++++++++++
> 2 files changed, 14 insertions(+)
>
> diff --git a/drivers/md/dm-rq.c b/drivers/md/dm-rq.c
> index c9e44ac1f9a6..21d5c1784d0c 100644
> --- a/drivers/md/dm-rq.c
> +++ b/drivers/md/dm-rq.c
> @@ -408,6 +408,7 @@ static int map_request(struct dm_rq_target_io *tio)
> ret = dm_dispatch_clone_request(clone, rq);
> if (ret == BLK_STS_RESOURCE || ret == BLK_STS_DEV_RESOURCE) {
> blk_rq_unprep_clone(clone);
> + blk_mq_cleanup_rq(clone);
> tio->ti->type->release_clone_rq(clone, &tio->info);
> tio->clone = NULL;
> return DM_MAPIO_REQUEUE;
Requiring upper layer driver (dm-rq) to explicitly call blk_mq_cleanup_rq()
seems wrong. In this instance tio->ti->type->release_clone_rq()
(dm-mpath's multipath_release_clone) calls blk_put_request(). Why can't
blk_put_request(), or blk_mq_free_request(), call blk_mq_cleanup_rq()?
Not looked at the cpu hotplug case you mention, but my naive thought is
it'd be pretty weird to also sprinkle a call to blk_mq_cleanup_rq() from
that specific "dead hctx" code path.
Mike
next prev parent reply other threads:[~2019-07-18 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 3:25 [PATCH 0/2] block/scsi/dm-rq: fix leak of request private data in dm-mpath Ming Lei
2019-07-18 3:25 ` [PATCH 1/2] blk-mq: add callback of .cleanup_rq Ming Lei
2019-07-18 14:52 ` Mike Snitzer [this message]
2019-07-19 1:35 ` Ming Lei
2019-07-19 12:26 ` Mike Snitzer
2019-07-18 3:25 ` [PATCH 2/2] scsi: implement .cleanup_rq callback Ming Lei
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=20190718145201.GA2305@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dm-devel@redhat.com \
--cc=emilne@redhat.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=jejb@linux.ibm.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).