All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Tejun Heo <htejun@gmail.com>
Cc: stable@kernel.org,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	Michael Tokarev <mjt@tls.msk.ru>, Jeff Garzik <jeff@garzik.org>,
	Diego Torres <dtorres@coral.dnsalias.org>
Subject: Re: [stable] [PATCH -stable] libata: kill spurious NCQ completion detection
Date: Tue, 11 Dec 2007 14:51:49 -0800	[thread overview]
Message-ID: <20071211225149.GB17643@kroah.com> (raw)
In-Reply-To: <4759E47B.8000108@gmail.com>

On Sat, Dec 08, 2007 at 09:25:31AM +0900, Tejun Heo wrote:
> Spurious NCQ completion detection implemented in ahci was incorrect.
> On AHCI receving and processing FISes and raising interrupts are not
> interlocked and spurious interrupts are expected.
> 
> For example, if an interrupt occurs while interrupt handler is running
> and the running interrupt handler handles the event the new IRQ
> indicated, after IRQ handler finishes, it will be executed again
> because IRQ pending bit is set by the new interrupt but there won't be
> anything to process.
> 
> Please read the following message for more information.
> 
>   http://article.gmane.org/gmane.linux.ide/26012
> 
> This patch...

Is this already in Linus's tree?  Is this for 2.6.23-stable, and/or
older ones too?

thanks,

greg k-h

  reply	other threads:[~2007-12-11 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-08  0:25 [PATCH -stable] libata: kill spurious NCQ completion detection Tejun Heo
2007-12-11 22:51 ` Greg KH [this message]
2007-12-11 23:30   ` [stable] " Tejun Heo
2007-12-13  6:03 ` patch libata-kill-spurious-ncq-completion-detection.patch queued to -stable tree gregkh
2007-12-13  6:11 ` gregkh

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=20071211225149.GB17643@kroah.com \
    --to=greg@kroah.com \
    --cc=dtorres@coral.dnsalias.org \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --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 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.