[V2] cxl: Allow release of contexts which have been OPENED but not STARTED

Michael Ellerman mpe at ellerman.id.au
Thu Aug 20 18:38:11 AEST 2015

On Tue, 2015-18-08 at 23:27:18 UTC, Andrew Donnellan wrote:
> If we open a context but do not start it (either because we do not attempt
> to start it, or because it fails to start for some reason), we are left
> with a context in state OPENED. Previously, cxl_release_context() only
> allowed releasing contexts in state CLOSED, so attempting to release an
> OPENED context would fail.
> In particular, this bug causes available contexts to run out after some EEH
> failures, where drivers attempt to release contexts that have failed to
> start.
> Allow releasing contexts in any state with a value lower than STARTED, i.e.
> OPENED or CLOSED (we can't release a STARTED context as it's currently
> using the hardware, and we assume that contexts in any new states which may
> be added in future with a value higher than STARTED are also unsafe to
> release).
> Cc: stable at vger.kernel.org
> Fixes: 6f7f0b3df6d4 ("cxl: Add AFU virtual PHB and kernel API")
> Signed-off-by: Andrew Donnellan <andrew.donnellan at au1.ibm.com>
> Signed-off-by: Daniel Axtens <dja at axtens.net>
> Acked-by: Ian Munsie <imunsie at au1.ibm.com>

Applied to powerpc next, thanks.



More information about the Linuxppc-dev mailing list