linux-kernel - Re: [PATCH 0/0] Power domain and clock domain patches for omap

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]

Message-ID: <alpine.DEB.1.00.0808200034010.26647@utopia.booyaka.com>
Date:	Wed, 20 Aug 2008 00:38:20 -0600 (MDT)
From:	Paul Walmsley <paul@...an.com>
To:	Dmitry Baryshkov <dbaryshkov@...il.com>
cc:	linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.arm.linux.org.uk
Subject: Re: [PATCH 0/0] Power domain and clock domain patches for omap

Hello Dmitry,

On Tue, 19 Aug 2008, Dmitry Baryshkov wrote:

> There is one major flaw IMO in this code. Please correct me if I'm wrong:
> Driver A: powerdomain_register()
> Driver B: powerdomain_get()
> Driver A: powerdomain_unregister()
> 
> Then Driver B has a reference to unregistered domain. And as powerdomains
> lack any type of refcounting this can lead to any type of memory access
> bugs if Driver A is unloaded from the kernel.

At this point, only OMAP kernel init code registers powerdomains in 
arch/arm/mach-omap2/io.c.  It's not intended that driver code will 
manipulate or even know about these.

Thanks for the comments,

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