From: Tejun Heo <tj@kernel.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Neil Brown <neilb@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] use after free bug in __blkdev_get
Date: Mon, 26 Oct 2009 13:55:54 +0100 [thread overview]
Message-ID: <4AE59C5A.1020305@kernel.org> (raw)
In-Reply-To: <20091026072607.GZ10727@kernel.dk>
Jens Axboe wrote:
> On Mon, Oct 26 2009, Neil Brown wrote:
>>
>> commit 0762b8bde9729f10f8e6249809660ff2ec3ad735
>> (from 14 months ago) introduced a use-after-free bug which has just
>> recently started manifesting in my md testing.
>> I tried git bisect to find out what caused the bug to start
>> manifesting, and it could have been the recent change to
>> blk_unregister_queue (48c0d4d4c04) but the results were inconclusive.
>>
>> This patch certainly fixes my symptoms and looks correct as the two
>> calls are now in the same order as elsewhere in that function.
>>
>> Signed-off-by: NeilBrown <neilb@suse.de>
Oops, thanks for catching it.
Acked-by: Tejun Heo <tj@kernel.org>
--
tejun
prev parent reply other threads:[~2009-10-26 12:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 5:03 [PATCH] use after free bug in __blkdev_get Neil Brown
2009-10-26 7:26 ` Jens Axboe
2009-10-26 12:55 ` Tejun Heo [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=4AE59C5A.1020305@kernel.org \
--to=tj@kernel.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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