From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: petkovbb@gmail.com
Cc: Michael Roth <mroth@nessie.de>, linux-kernel@vger.kernel.org
Subject: Re: Bug in 2.6.29 ide-cd: Kernel freeze: bisected + unacceptable workaround
Date: Tue, 31 Mar 2009 20:01:45 +0200 [thread overview]
Message-ID: <200903312001.45960.bzolnier@gmail.com> (raw)
In-Reply-To: <20090331074508.GA16403@liondog.tnic>
On Tuesday 31 March 2009, Borislav Petkov wrote:
> Hi,
>
> > > @Bart: can you take at look at this. Somehow, if the device is behind a
> > > PCI IDE controller, the order of issuing the command and enabling DMA is
> > > important. Seen something like that before?
> >
> > Spec is unclear on the ordering but empirically it seems that some hosts
> > may need packet command to start DMA. I think that we should proceed with
> > your patch (please repost with patch description) and also apply the same
> > change to the rest of ATAPI devices in a subsequent patch.
>
> Why two patches, do we really need to differentiate between ide-cd and
> other ATAPI devices? Besides the patch is so simple: 4 lines moved up.
Good engineering practice -- we've changed only ide-cd in 2.6.29 so we
should start with reverting the change and backporting it to -stable.
Fixing other ATAPI devices can be handled later and preferrably after
testing them first -- who knows if there are no devices which depend on
the reverse order of doing things or that it won't uncover/trigger some
other problem. Feel free to call me (over-)paranoid... :)
However based on later comments from Alan and the current libata code
I feel that we should be pretty safe in this particular case so we may
as well fix everything in one go.
> Anyway, I lightly tested it with ide-cd and ide-floppy and both seem to
> take it ok. Also, if I remember correctly, the original ide-cd behavior
> was to issue the command and _then_ start DMA so we're back to that. I
> guess now we should be concerned whether the other ATAPI devices can
> handle the reverse situation where you first issue a command and _then_
> start DMA.. Hmm...
>
> --
> From: Borislav Petkov <petkovbb@gmail.com>
> Date: Tue, 31 Mar 2009 09:36:44 +0200
> Subject: [PATCH] ide-atapi: start DMA after issuing a packet command
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Transfer-Encoding: 8bit
>
> Apparently¹, some ATAPI devices want to see the packet command first
> before enabling DMA otherwise they simply hang indefinitely. Reorder the
> two steps and start DMA only after having issued the command first.
>
> [1] http://marc.info/?l=linux-kernel&m=123835520317235&w=2
I added "Reported-by:" here
> Signed-off-by: Borislav Petkov <petkovbb@gmail.com>
applied
prev parent reply other threads:[~2009-03-31 17:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-29 19:25 Bug in 2.6.29 ide-cd: Kernel freeze: bisected + unacceptable workaround Michael Roth
2009-03-29 20:13 ` Borislav Petkov
2009-03-29 21:37 ` Michael Roth
2009-03-30 7:27 ` Borislav Petkov
2009-03-30 11:10 ` Michael Roth
2009-03-30 11:38 ` Michael Roth
2009-03-30 11:50 ` Michael Roth
2009-03-30 20:28 ` Bartlomiej Zolnierkiewicz
2009-03-31 7:45 ` Borislav Petkov
2009-03-31 11:28 ` Alan Cox
2009-03-31 12:35 ` Michael Roth
2009-03-31 14:06 ` Borislav Petkov
2009-03-31 18:01 ` Bartlomiej Zolnierkiewicz [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=200903312001.45960.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mroth@nessie.de \
--cc=petkovbb@gmail.com \
/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