From: Linus Torvalds <torvalds@linux-foundation.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: RESEND: [PATCH] libata-sff: Fix oops reported in kerneloops.org for pnp devices with no ctl
Date: Thu, 29 May 2008 14:13:26 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0805291403030.3873@woody.linux-foundation.org> (raw)
In-Reply-To: <20080529191920.12609c32@core>
On Thu, 29 May 2008, Alan Cox wrote:
>
> And this is how a revised one would look.
Ok, this looks nicer, but how about:
> +static u8 ata_sff_irq_status(struct ata_port *ap)
> +{
> + u8 status;
> +
> + if (ap->ops->sff_check_altstatus || ap->ioaddr.altstatus_addr) {
> + status = ata_sff_altstatus(ap);
This here is all about not oopsing in ata_sff_altstatus(), ie just knowing
about the bug.
Why not just fix ata_sff_altstatus(), instead of causing these kinds of
problems downstream?
If you don't want to read the status register, fine. But at least do
something like
- make ata_sff_altstatus static, since it's useless and dangerous to call
otherwise (ie make the exported interfaces be the nicer higher-level
ones that are sane)
- and make it just return 0 if the altstatus register doesn't exist.
At that point, both 'ata_sff_irq_status()' and 'ata_sff_sync()' can just
use ata_sff_altstatus() directly, *without* having to check that altstatus
setup by hand, or re-implement the function just because it was buggy and
broken to begin with.
So now ata_sff_irq_status() just becomes
static u8 ata_sff_irq_status(struct ata_port *ap)
{
u8 status;
status = ata_sff_altstatus(ap);
if (status & ATA_BUSY)
return status;
/* Clear INTRQ latch */
status = ata_sff_check_status(ap);
return status;
}
and if there was no altstatus register, everything is fine because
"ata_sff_altstatus()" was safe and returned 0 (and not ATA_BUSY).
Or feel free and make it return ATA_INVALID, which has a value of 0x100,
or something - it still won't be busy, and it will clearly not be a byte
read, so people *can* check for "no altstatus existed" if they want to.
Similarly, 'ata_sff_sync()' just becomes
void ata_sff_sync(struct ata_port *ap)
{
ata_sff_altstatus();
}
and 'ata_sff_pause()' becomes
void ata_sff_pause(struct ata_port *ap)
{
ata_sff_altstatus();
ndelay(400);
}
and again, if there is no altstatus register, that's a low-level driver
issue.
Linus
next prev parent reply other threads:[~2008-05-29 21:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 16:25 Alan Cox
2008-05-29 17:04 ` Linus Torvalds
2008-05-29 17:46 ` Jeff Garzik
2008-05-29 18:04 ` Linus Torvalds
2008-05-29 18:13 ` Jeff Garzik
2008-05-29 18:29 ` Alan Cox
2008-05-29 18:19 ` Alan Cox
2008-05-29 21:13 ` Linus Torvalds [this message]
2008-05-29 21:19 ` Alan Cox
2008-05-29 18:02 ` Alan Cox
2008-05-29 18:25 ` Jeff Garzik
2008-05-29 18:38 ` Alan Cox
2008-05-29 19:46 ` Linus Torvalds
2008-05-29 20:18 ` Alan Cox
2008-05-29 18:42 ` Alan Cox
2008-05-29 19:31 ` Jeff Garzik
2008-05-29 21:10 ` [RFC PATCH] " Alan Cox
2008-05-29 21:37 ` Alan Cox
2008-05-29 21:57 ` Jeff Garzik
2008-05-29 21:57 ` Alan Cox
2008-05-30 22:14 ` Jeff Garzik
2008-06-04 10:45 ` Jeff Garzik
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=alpine.LFD.1.10.0805291403030.3873@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®