public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Greg KH <greg@kroah.com>, "Michael S. Tsirkin" <mst@redhat.com>,
	"Hans J. Koch" <hjk@hansjkoch.de>,
	Chris Wright <chrisw@redhat.com>,
	Anthony Foiani <anthony.foiani@gmail.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	stable@kernel.org
Subject: Re: [stable] [PATCH] uio/gen-pci: don't enable interrupts in ISR
Date: Tue, 23 Aug 2011 12:57:42 +0200	[thread overview]
Message-ID: <20110823105727.GA29209@local> (raw)
In-Reply-To: <20110823084005.GB20979@linutronix.de>

On Tue, Aug 23, 2011 at 10:40:05AM +0200, Sebastian Andrzej Siewior wrote:
> * Greg KH | 2011-08-22 17:49:43 [-0700]:
> 
> >> > Cc: Anthony Foiani <anthony.foiani@gmail.com>
> >
> >Why, it's not fixing a bug that anyone hits, right?
> 
> "earlier" the interrupt handler was executed either with interrupts
> enabled or disabled if IRQF_DISABLED was specified. Later the latter
> become default even if IRQF_DISABLED was not specified. This lead to the
> splat Anthony reported because the irq handler was entered with IRQs
> disabled and the ISR enabled them via spin_unlock_irq(). My initial
> patch simply used spin_unlock_irqrestore() (and its counterpart) to have
> the same state as we had.
> 
> So the bug Anthony hit was that the interrupts were enabled where they
> should not be.
> 
> >greg k-h
> 
> Sebastian
> 

Greg, I'll change the commit message so that it becomes clear, and send
you a pull request.

There is also one more UIO patch pending. Do you want a separate branch
for -stable, or can you cherry-pick that from one UIO branch?

Thanks,
Hans


  reply	other threads:[~2011-08-23 10:58 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
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 [this message]
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=20110823105727.GA29209@local \
    --to=hjk@hansjkoch.de \
    --cc=anthony.foiani@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=chrisw@redhat.com \
    --cc=greg@kroah.com \
    --cc=gregkh@suse.de \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox