From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>, NeilBrown <neilb@suse.de>,
Stefan Seyfried <stefan.seyfried@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] blk-mq: free hctx->ctxs in queue's release handler
Date: Tue, 09 Jun 2015 15:32:13 -0600 [thread overview]
Message-ID: <55775B5D.9010507@kernel.dk> (raw)
In-Reply-To: <CACVXFVPCfjFzX=g5M-=6N0qAYYgTV0FP_sT_7DWaAse9gkYv5A@mail.gmail.com>
On 06/09/2015 03:28 AM, Ming Lei wrote:
> Hi Jens,
>
> Could you consider this patch for v4.1?
>
> http://marc.info/?l=linux-kernel&m=143342792910832&w=2
>
> The issue is one obvious use-after-free and can be reproduced easily
> via 'sudo modprobe loop;sleep 1;sudo rmmod loop' on linus tree:
>
> http://kernel.ubuntu.com/~ming/block/bug/4.1-rc7-blk-mq-oops.txt
I'll pull it in, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2015-06-09 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 9:28 [PATCH v1] blk-mq: free hctx->ctxs in queue's release handler Ming Lei
2015-06-09 21:32 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-04 14:25 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=55775B5D.9010507@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=stefan.seyfried@googlemail.com \
--cc=tom.leiming@gmail.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