linux-kernel - Re: [PATCH] blk-mq: fix hctx/ctx kobject use-after-free

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 20 Jan 2015 12:30:18 -0700
From:	Jens Axboe <axboe@...com>
To:	Ming Lei <ming.lei@...onical.com>, <linux-kernel@...r.kernel.org>
CC:	Sasha Levin <sasha.levin@...cle.com>
Subject: Re: [PATCH] blk-mq: fix hctx/ctx kobject use-after-free

On 01/19/2015 08:00 PM, Ming Lei wrote:
> The kobject memory shouldn't have been freed before the kobject
> is released because driver core can access it freely before its
> release.
>
> This patch frees hctx in its release callback. For ctx, they
> share one single per-cpu variable which is associated with
> the request queue, so free ctx in q->mq_kobj's release handler.
>
> Signed-off-by: Sasha Levin <sasha.levin@...cle.com>
> (fix ctx kobjects)
> Signed-off-by: Ming Lei <ming.lei@...onical.com>

Thanks Ming, applied.

-- 
Jens Axboe

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/