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]
Message-ID: <20140602210117.GO31751@sirena.org.uk>
Date:	Mon, 2 Jun 2014 22:01:17 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>
Cc:	lee.jones@...aro.org, sameo@...ux.intel.com,
	patches@...nsource.wolfsonmicro.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mfd: core: Add the option to order destruction of
 MFD cells

On Mon, Jun 02, 2014 at 10:01:43AM +0100, Charles Keepax wrote:
> Sometimes MFD children will have interdependancies. For example an MFD
> device might contain a regulator cell and another cell which requires
> that regulator to function. Probe deferral will ensure that these
> devices probe in the correct order, however currently nothing ensures
> they are destroyed in the correct order. As such it is possible for a
> cell to be destroyed whilst another cell still expects it to exist. For
> example the cell mentioned earlier would attempt to do a regulator_put
> as part of its own tear-down but the regulator may have already been
> destroyed.

Probe deferral is supposed to handle removal too, we're supposed to be
able to walk the device list in reverse order and everything just work.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ