All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [patch] sparc64: enable IRQs on error paths
Date: Fri, 25 Nov 2016 20:45:24 +0000	[thread overview]
Message-ID: <20161125204524.GA27864@ravnborg.org> (raw)
In-Reply-To: <20161125111054.GE5938@mwanda>

Hi Dan.

On Fri, Nov 25, 2016 at 02:12:51PM +0300, Dan Carpenter wrote:
> There are several error paths where we should enable IRQs but we don't.
> 
> Fixes: bb620c3d3925 ("sparc: Make sparc64 use scalable lib/iommu-common.c functions")
> Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>

Please use a more descriptive subject such as:
sparc64: restore irq in error paths in iommu

> ---
> Not tested.
> 
> diff --git a/arch/sparc/kernel/pci_sun4v.c b/arch/sparc/kernel/pci_sun4v.c
> index 06981cc7..274df7a 100644
> --- a/arch/sparc/kernel/pci_sun4v.c
> +++ b/arch/sparc/kernel/pci_sun4v.c
> @@ -230,12 +230,16 @@ static void *dma_4v_alloc_coherent(struct device *dev, size_t size,
>  
>  	for (n = 0; n < npages; n++) {
>  		long err = iommu_batch_add(first_page + (n * PAGE_SIZE), mask);
> -		if (unlikely(err < 0L))
> +		if (unlikely(err < 0L)) {
> +			local_irq_restore(flags);
>  			goto iommu_map_fail;
> +		}
>  	}

Locate all cleanup after the iommu_map_fail label.

As it is now the irq_restore is on the error site
and the free() is at the error label.

It is very confusing that half of the recovery is in one
place and the other in another place.

	Sam

  parent reply	other threads:[~2016-11-25 20:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 11:12 [patch] sparc64: enable IRQs on error paths Dan Carpenter
2016-11-25 12:32 ` Sowmini Varadhan
2016-11-25 13:01 ` Dan Carpenter
2016-11-25 13:11 ` Sowmini Varadhan
2016-11-25 13:46 ` Dan Carpenter
2016-11-25 13:57 ` Sowmini Varadhan
2016-11-25 20:45 ` Sam Ravnborg [this message]
2016-11-25 21:06 ` tndave
2016-11-25 21:11 ` Dan Carpenter

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=20161125204524.GA27864@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=kernel-janitors@vger.kernel.org \
    /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.