From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Hancock <hancockr@shaw.ca>, Alexander <aledin@mail.ru>,
linux-kernel@vger.kernel.org, ide <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Tejun Heo <htejun@gmail.com>
Subject: Re: PROBLEM REMAINS: [sata_nv ADMA breaks ATAPI] Crash on accessing DVD-RAM
Date: Sun, 13 Jan 2008 09:38:45 -0600 [thread overview]
Message-ID: <1200238725.3179.16.camel@localhost.localdomain> (raw)
In-Reply-To: <20080113133317.50ad4bda@lxorguk.ukuu.org.uk>
On Sun, 2008-01-13 at 13:33 +0000, Alan Cox wrote:
> > Other than that, I guess the solutions would be to just set a 32-bit
> > mask on the device if either port has an ATAPI device connected (which
> > is fairly ugly, considering that you could do things like hotplug an
> > ATAPI device when the other port was in use, for example), or do
> > something to prevent requests from reaching this point with >4GB
> > addresses in the first place..
>
> With 2.6.24 almost released I think that is a must do for the moment and
> since we also have hotplugging fo devices it might be easier for .24 to
> just set a 32bit DMA mask and be done with it, then fix it later.
Yes, I concur for the short term. The other two possible courses of
action either involve long discussions (the different device one) or
you'll never quite be sure you got all the paths (the GFP_DMA32 one).
At least with this one, you know everything will work.
James
next prev parent reply other threads:[~2008-01-13 15:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.krOVfyFmB2aqGjJIoHCLmQxecWc@ifi.uio.no>
2008-01-11 5:46 ` PROBLEM REMAINS: [sata_nv ADMA breaks ATAPI] Crash on accessing DVD-RAM Robert Hancock
2008-01-12 8:25 ` Alexander
2008-01-12 19:25 ` Robert Hancock
2008-01-12 20:35 ` James Bottomley
2008-01-12 23:04 ` Robert Hancock
2008-01-12 23:27 ` James Bottomley
2008-01-13 1:38 ` Robert Hancock
2008-01-13 3:12 ` James Bottomley
2008-01-13 13:33 ` Alan Cox
2008-01-13 15:38 ` James Bottomley [this message]
2008-01-13 16:29 ` Alan Cox
2008-01-13 16:51 ` James Bottomley
2008-01-15 1:41 ` Robert Hancock
2008-01-15 2:23 ` James Bottomley
2008-02-01 0:09 ` Robert Hancock
2008-02-01 9:59 ` Alexander
2008-02-04 8:29 ` Alexander
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=1200238725.3179.16.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=aledin@mail.ru \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).