All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Fajun Chen <fajunchen@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	Mark Lord <liml@rtr.ca>, Tejun Heo <htejun@gmail.com>
Subject: Re: PATA Sil680 Disabling IRQ
Date: Thu, 28 Feb 2008 23:10:02 +0000	[thread overview]
Message-ID: <20080228231002.325c9e1d@core> (raw)
In-Reply-To: <8202f4270802281411j747bf96dx34ff81c4d192d417@mail.gmail.com>

> For most of unsupported commands, it will be aborted by drive.
> However, for some unsupported commands, it may not.  I suspect these
> bad commands are the new ones in ATA8 issued to some drives with old
> firmware. For instance, can you try command 0x5E (Trusted Send PIO
> data out) with sector count set to 1 and see what happens?

Well the kernel as of 2.6.24 defaults to blocking treacherous computing
commands 8)

> The blame is probably on drives which should have aborted these
> commands. But the reality is that libata will handle variety of drives
> including the ones with old firmware.  So the question here is whether
> libata PATA code can be more fault tolerate. It seems the weakest link
> is on PATA PIO since I have not been able to reproduce the IRQ
> disabling problem on DMA operations.

If you send crap to a drive you will get junk as a result. Only the
superuser can do this so that behaviour is fine. The superuser can also
crash the machine a million other ways. End users cannot send arbitary
commands to the drive.

Ditto they may know that an "unsupported" command for their ATA version
is actually a vendor private command for the specific drive they have.

Alan

  parent reply	other threads:[~2008-02-28 23:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27  0:47 PATA Sil680 Disabling IRQ Fajun Chen
2008-02-27  0:58 ` Jeff Garzik
2008-02-28  0:20   ` Fajun Chen
2008-02-28 20:22     ` Alan Cox
2008-02-28 22:11       ` Fajun Chen
2008-02-28 22:24         ` Jeff Garzik
2008-02-28 23:10         ` Alan Cox [this message]
2008-02-29  1:07           ` Fajun Chen
2008-02-29 11:21             ` Alan Cox

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=20080228231002.325c9e1d@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=fajunchen@gmail.com \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=liml@rtr.ca \
    --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 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.