From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <htejun@gmail.com>
Cc: IDE/ATA development list <linux-ide@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Berck E. Nash" <flyboy@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] libata: ignore EH scheduling during initialization
Date: Fri, 11 May 2007 18:10:05 -0400 [thread overview]
Message-ID: <4644E9BD.3070607@garzik.org> (raw)
In-Reply-To: <46370D57.1070504@gmail.com>
Tejun Heo wrote:
> libata enables SCSI host during ATA host activation which happens
> after IRQ handler is registered and IRQ is enabled. All ATA ports are
> in frozen state when IRQ is enabled but frozen ports may raise limited
> number of IRQs after being frozen - IOW, ->freeze() is not responsible
> for clearing pending IRQs. During normal operation, the IRQ handler
> is responsible for clearing spurious IRQs on frozen ports and it
> usually doesn't require any extra code.
>
> Unfortunately, during host initialization, the IRQ handler can end up
> scheduling EH for a port whose SCSI host isn't initialized yet. This
> results in OOPS in the SCSI midlayer. This is relatively short window
> and scheduling EH for probing is the first thing libata does after
> initialization, so ignoring EH scheduling until initialization is
> complete solves the problem nicely.
>
> This problem was spotted by Berck E. Nash in the following thread.
>
> http://thread.gmane.org/gmane.linux.kernel/519412
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Berck E. Nash <flyboy@gmail.com>
applied
prev parent reply other threads:[~2007-05-11 22:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 9:50 [PATCH] libata: ignore EH scheduling during initialization Tejun Heo
2007-05-11 22:10 ` Jeff Garzik [this message]
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=4644E9BD.3070607@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=flyboy@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-ide@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).