linux-kernel - Re: [PATCH] blkio: Release blkg infrastructure only after last policy is deactivated.

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Jun 2014 17:09:30 -0400
From:	Tejun Heo <tj@...nel.org>
To:	shirishpargaonkar@...il.com
Cc:	linux-kernel@...r.kernel.org, vgoyal@...hat.com,
	Shirish Pargaonkar <spargaonkar@...e.com>
Subject: Re: [PATCH] blkio: Release blkg infrastructure only after last
 policy is deactivated.

Hello,

On Mon, Jun 23, 2014 at 01:52:25PM -0500, shirishpargaonkar@...il.com wrote:
> From: Shirish Pargaonkar <spargaonkar@...e.com>
> 
> Release blkg infrastructure only after last policy is deactivated
> (i.e. let blkg_destroy_all() be called only from blkcg_deactivate_policy())
> 
> Otherwise, module can oops because root_blkg gets assigned NULL during
> cleanup and we attempt draining the service queues via root_blkg afterwords.

I'm not sure this fix makes sense.  Cleanup path oopses on an already
freed resource.  How can the solution be not freeing?  Why not simply
make blkcg_drain_queue() bail if the blkgs are all destroyed?  The
whole thing is fully synchronized with the queuelock, right?

Can you please also cc Jens when you post the next iteration?

Thanks.

-- 
tejun
--
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/