All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Chris Wright <chrisw@redhat.com>,
	"Hans J. Koch" <hjk@hansjkoch.de>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Anthony Foiani <anthony.foiani@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] uio/gen-pci: don't enable interrupts in ISR
Date: Fri, 5 Aug 2011 00:04:13 +0300	[thread overview]
Message-ID: <20110804210413.GA29222@redhat.com> (raw)
In-Reply-To: <20110804204606.GA19724@linutronix.de>

On Thu, Aug 04, 2011 at 10:46:06PM +0200, Sebastian Andrzej Siewior wrote:
> As reported by Anthony in a short way:
> 
> |irq 17 handler uio_interrupt+0x0/0x68 enabled interrupts
> |NIP [c0069d84] handle_irq_event_percpu+0x260/0x26c
> 
> The problem here is that spin_unlock_irq() enables the interrupts which
> is a no-no in interrupt context because they always run with interrupts
> disabled. This is the case even if IRQF_DISABLED has not been specified
> since v2.6.35. Therefore this patch uses simple spin_locks().
> 
> Looking at it further here is only one spot where the lock is hold. So
> giving the fact that an ISR is not reentrant and is not executed on two
> cpus at the same time why do we need a lock here?

I'm not sure anymore. I think the idea was to use
it for synchronization down the road somehow,
but it never materialized. Let's drop that lock completely.

> The driver lacks of ->irqcontrol function so I guess the interrupt is
> enabled via direct PCI-access in userland.

Through sysfs.

> So there is _no_ protection
> against read-modify-write of user vs kernel so even that
> pci_block_user_cfg_access() is kinda pointless.

I didn't get that. pci_block_user_cfg_access is to prevent
sysfs access while we read modify-write the command register.
Isn't it effective for that?

> pci_block_user_cfg_access() in open() + ->irqcontrol() should fix this.

Why block in open? We don't access the device there, do we?

> Since changes the API of this driver I leave it up to the relevant users
> what to do.

Yes, changing API's not good, we need to keep existing userspace happy.

> Cc: <stable@kernel.org> # .35 and later
> Reported-and-Tested-by: Anthony Foiani <anthony.foiani@gmail.com>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>  drivers/uio/uio_pci_generic.c |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/uio/uio_pci_generic.c b/drivers/uio/uio_pci_generic.c
> index fc22e1e..5c82681 100644
> --- a/drivers/uio/uio_pci_generic.c
> +++ b/drivers/uio/uio_pci_generic.c
> @@ -57,7 +57,7 @@ static irqreturn_t irqhandler(int irq, struct uio_info *info)
>  	BUILD_BUG_ON(PCI_COMMAND % 4);
>  	BUILD_BUG_ON(PCI_COMMAND + 2 != PCI_STATUS);
>  
> -	spin_lock_irq(&gdev->lock);
> +	spin_lock(&gdev->lock);
>  	pci_block_user_cfg_access(pdev);
>  
>  	/* Read both command and status registers in a single 32-bit operation.
> @@ -83,7 +83,7 @@ static irqreturn_t irqhandler(int irq, struct uio_info *info)
>  done:
>  
>  	pci_unblock_user_cfg_access(pdev);
> -	spin_unlock_irq(&gdev->lock);
> +	spin_unlock(&gdev->lock);
>  	return ret;
>  }
>  
> -- 
> 1.7.4.4

  reply	other threads:[~2011-08-04 21:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04 20:46 [PATCH] uio/gen-pci: don't enable interrupts in ISR Sebastian Andrzej Siewior
2011-08-04 21:04 ` Michael S. Tsirkin [this message]
2011-08-05  0:15   ` Hans J. Koch
2011-08-08  6:24     ` Michael S. Tsirkin
2011-08-08 17:19       ` Hans J. Koch
2011-08-09 11:37         ` Michael S. Tsirkin
2011-08-09 18:53           ` Hans J. Koch
2011-08-10  8:40             ` Michael S. Tsirkin
2011-08-23  0:49               ` [stable] " Greg KH
2011-08-23  8:40                 ` Sebastian Andrzej Siewior
2011-08-23 10:57                   ` Hans J. Koch
2011-08-23 11:00                     ` Hans J. Koch
2011-08-05 19:18   ` Sebastian Andrzej Siewior
2011-08-08  6:40     ` Michael S. Tsirkin
2011-08-09 11:43       ` Sebastian Andrzej Siewior
2011-08-09 12:02         ` Michael S. Tsirkin
2011-08-10  8:33           ` Sebastian Andrzej Siewior

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=20110804210413.GA29222@redhat.com \
    --to=mst@redhat.com \
    --cc=anthony.foiani@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=chrisw@redhat.com \
    --cc=gregkh@suse.de \
    --cc=hjk@hansjkoch.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@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.