From: Jens Axboe <axboe@kernel.dk>
To: Yang Yang <yang.yang@vivo.com>,
Bart Van Assche <bvanassche@acm.org>,
Hannes Reinecke <hare@suse.com>, Ming Lei <ming.lei@redhat.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: onlyfever@icloud.com
Subject: Re: [PATCH] blk-mq: move cancel of hctx->run_work to the front of blk_exit_queue
Date: Fri, 9 Oct 2020 12:46:43 -0600 [thread overview]
Message-ID: <ab2c4655-0ae0-f5c8-2d59-5e699fe9059e@kernel.dk> (raw)
In-Reply-To: <20201009080015.3217-1-yang.yang@vivo.com>
On 10/9/20 2:00 AM, Yang Yang wrote:
> blk_exit_queue will free elevator_data, while blk_mq_run_work_fn
> will access it. Move cancel of hctx->run_work to the front of
> blk_exit_queue to avoid use-after-free.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-10-09 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 8:00 [PATCH] blk-mq: move cancel of hctx->run_work to the front of blk_exit_queue Yang Yang
2020-10-09 9:46 ` Ming Lei
2020-10-09 18:46 ` Jens Axboe [this message]
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=ab2c4655-0ae0-f5c8-2d59-5e699fe9059e@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hare@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=onlyfever@icloud.com \
--cc=yang.yang@vivo.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 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).