All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Cyril Bur <cyrilbur@gmail.com>,
	linuxppc-dev@lists.ozlabs.org, linux-mtd@lists.infradead.org
Cc: stewart@linux.vnet.ibm.com, dwmw2@infradead.org
Subject: Re: [PATCH 5/5] mtd: powernv_flash: Use opal_async_wait_response_interruptible()
Date: Sat, 08 Jul 2017 14:59:57 -0500	[thread overview]
Message-ID: <1499543997.29707.6.camel@kernel.crashing.org> (raw)
In-Reply-To: <20170629065413.19845-6-cyrilbur@gmail.com>

On Thu, 2017-06-29 at 16:54 +1000, Cyril Bur wrote:
> The OPAL calls performed in this driver shouldn't be using
> opal_async_wait_response() as this performs a wait_event() which, on
> long running OPAL calls could result in hung task warnings. wait_event()
> also prevents timely signal delivery which is also undesirable.
> 
> This patch also attempts to quieten down the use of dev_err() when
> errors haven't actually occurred and also to return better information up
> the stack rather than always -EIO.

So what happens when you get a signal then ? The async op is still in
progress, will the callers properly handle that ?

For example, for a read, OPAL will potentially still be writing to
the destination buffer. Are the callers expecting this ?

That sounds very broken to me ....

You should simply limit the amount of flash that can be affected by
a single call to avoid long hung tasks.

> Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
> ---
>  drivers/mtd/devices/powernv_flash.c | 18 +++++++++++-------
>  1 file changed, 11 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/mtd/devices/powernv_flash.c b/drivers/mtd/devices/powernv_flash.c
> index 7b41af06f4fe..a7c5ae2b2898 100644
> --- a/drivers/mtd/devices/powernv_flash.c
> +++ b/drivers/mtd/devices/powernv_flash.c
> @@ -88,19 +88,23 @@ static int powernv_flash_async_op(struct mtd_info *mtd, enum flash_op op,
>  	}
>  
>  	if (rc != OPAL_ASYNC_COMPLETION) {
> -		dev_err(dev, "opal_flash_async_op(op=%d) failed (rc %d)\n",
> -				op, rc);
> +		if (rc != OPAL_BUSY)
> +			dev_err(dev, "opal_flash_async_op(op=%d) failed (rc %d)\n",
> +					op, rc);
>  		opal_async_release_token(token);
> -		rc = -EIO;
> +		rc = opal_error_code(rc);
>  		goto out;
>  	}
>  
> -	rc = opal_async_wait_response(token, &msg);
> +	rc = opal_async_wait_response_interruptible(token, &msg);
>  	opal_async_release_token(token);
>  	mutex_unlock(&info->lock);
>  	if (rc) {
> -		dev_err(dev, "opal async wait failed (rc %d)\n", rc);
> -		return -EIO;
> +		if (rc == -ERESTARTSYS)
> +			rc = -EINTR;
> +		else
> +			dev_err(dev, "opal async wait failed (rc %d)\n", rc);
> +		return rc;
>  	}
>  
>  	rc = opal_get_async_rc(msg);
> @@ -109,7 +113,7 @@ static int powernv_flash_async_op(struct mtd_info *mtd, enum flash_op op,
>  		if (retlen)
>  			*retlen = len;
>  	} else {
> -		rc = -EIO;
> +		rc = opal_error_code(rc);
>  	}
>  
>  	return rc;

  parent reply	other threads:[~2017-07-08 20:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29  6:54 [PATCH 0/5] Allow opal-async waiters to get interrupted Cyril Bur
2017-06-29  6:54 ` [PATCH 1/5] powerpc/opal: Make __opal_async_{get, release}_token() static Cyril Bur
2017-06-29  6:54 ` [PATCH 2/5] powerpc/opal: Rework the opal-async interface Cyril Bur
2017-06-29  6:54 ` [PATCH 3/5] powerpc/opal: Add opal_async_wait_response_interruptible() to opal-async Cyril Bur
2017-06-29  6:54 ` [PATCH 4/5] powerpc/powernv: Add OPAL_BUSY to opal_error_code() Cyril Bur
2017-06-29  6:54 ` [PATCH 5/5] mtd: powernv_flash: Use opal_async_wait_response_interruptible() Cyril Bur
2017-07-08  1:28   ` Brian Norris
2017-07-08 19:59   ` Benjamin Herrenschmidt [this message]
2017-07-09 23:58     ` Cyril Bur

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=1499543997.29707.6.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=cyrilbur@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=stewart@linux.vnet.ibm.com \
    /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.