All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Neuling <mikey@neuling.org>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Andrew Donnellan <andrew.donnellan@au1.ibm.com>,
	linuxppc-dev@ozlabs.org,  dja@axtens.net,
	benh@kernel.crashing.org, imunsie@au1.ibm.com
Subject: Re: [PATCH] cxl: Allow release of contexts which have been OPENED but not STARTED
Date: Tue, 18 Aug 2015 09:23:10 -0700	[thread overview]
Message-ID: <1439914990.1628.6.camel@neuling.org> (raw)
In-Reply-To: <1439889583.31374.1.camel@ellerman.id.au>

On Tue, 2015-08-18 at 19:19 +1000, Michael Ellerman wrote:
> On Tue, 2015-08-18 at 16:30 +1000, Andrew Donnellan wrote:
> > If we open a context but do not start it (either because we do not atte=
mpt
> > 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.
> >=20
> > 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.
> >=20
> > Allow releasing contexts in any state other than STARTED, i.e. OPENED o=
r
> > CLOSED (we can't release a STARTED context as it's currently using the
> > hardware).
> >=20
> > Cc: stable@vger.kernel.org
> > Fixes: 6f7f0b3df6d4 ("cxl: Add AFU virtual PHB and kernel API")
> > Signed-off-by: Andrew Donnellan <andrew.donnellan@au1.ibm.com>
> > Signed-off-by: Daniel Axtens <dja@axtens.net>
> > ---
> >  drivers/misc/cxl/api.c | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >=20
> > diff --git a/drivers/misc/cxl/api.c b/drivers/misc/cxl/api.c
> > index 6a768a9..1c520b8 100644
> > --- a/drivers/misc/cxl/api.c
> > +++ b/drivers/misc/cxl/api.c
> > @@ -59,7 +59,7 @@ EXPORT_SYMBOL_GPL(cxl_get_phys_dev);
> > =20
> >  int cxl_release_context(struct cxl_context *ctx)
> >  {
> > -	if (ctx->status !=3D CLOSED)
> > +	if (ctx->status =3D=3D STARTED)
> >  		return -EBUSY;
>=20
> So this doesn't break when you add a new state, is it worth writing it as=
:
>=20
> 	if (ctx->status >=3D STARTED)
> 		return -EBUSY;
>=20
> ?

Yeah I think that would be more future proof, although it won't make a
difference with the current code.

FWIW, looks good to me.

Mikey

  reply	other threads:[~2015-08-18 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18  6:30 [PATCH] cxl: Allow release of contexts which have been OPENED but not STARTED Andrew Donnellan
2015-08-18  6:36 ` Ian Munsie
2015-08-18  9:19 ` Michael Ellerman
2015-08-18 16:23   ` Michael Neuling [this message]
2015-08-18 23:10     ` Andrew Donnellan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1439914990.1628.6.camel@neuling.org \
    --to=mikey@neuling.org \
    --cc=andrew.donnellan@au1.ibm.com \
    --cc=benh@kernel.crashing.org \
    --cc=dja@axtens.net \
    --cc=imunsie@au1.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.