From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>
Subject: Re: SCSI breakage on non-cache coherent architectures
Date: Tue, 20 Nov 2007 06:53:04 +1100 [thread overview]
Message-ID: <1195501984.6970.1.camel@pasglop> (raw)
In-Reply-To: <20071119123240.GA12494@parisc-linux.org>
On Mon, 2007-11-19 at 05:32 -0700, Matthew Wilcox wrote:
> On Mon, Nov 19, 2007 at 04:35:23PM +1100, Benjamin Herrenschmidt wrote:
> > The other one I'm hitting now is that the SCSI layer nowadays embeds the
>
> 'nowadays'? It has always been so.
Wasn't it kmalloc'ed at one point ?
> > sense_buffer inside the scsi_cmnd structure without any kind of
> > alignment whatsoever. I've been hitting irregulary is a crash on SCSI command
> > completion that seems to be related to corruption of the "request"
> > pointer in struct scsi_cmnd and I think it might be the cause.
> > I'm now trying to setup a proper repro-case.
>
> What other drivers do is DMA to their own allocation and then memcpy to
> the sense buffer.
What "other drivers" ? Those architectures use the same drivers as
everything else.
> There is a movement to allocate the sense data as its own sg list, but
> I don't think that patch has even been posted yet.
I've seen code creating an sglist from the scsi_cmnd->sense_buffer and
passing that to drivers. That breaks.
Ben.
next prev parent reply other threads:[~2007-11-19 19:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 5:35 SCSI breakage on non-cache coherent architectures Benjamin Herrenschmidt
2007-11-19 8:38 ` David Miller
2007-11-19 19:51 ` Benjamin Herrenschmidt
2007-11-19 22:31 ` David Miller
2007-11-20 0:34 ` Benjamin Herrenschmidt
2007-11-20 0:46 ` David Miller
2007-11-20 0:55 ` Benjamin Herrenschmidt
2007-11-20 0:57 ` David Miller
2007-11-20 2:10 ` Roland Dreier
2007-11-20 2:35 ` Benjamin Herrenschmidt
2007-11-20 3:14 ` Benjamin Herrenschmidt
2007-11-20 19:35 ` James Bottomley
2007-11-20 8:29 ` Thomas Bogendoerfer
2007-11-20 14:36 ` James Bottomley
2007-11-20 20:05 ` Roland Dreier
2007-11-20 21:10 ` James Bottomley
2007-11-20 22:39 ` Benjamin Herrenschmidt
2007-11-20 23:09 ` James Bottomley
2007-11-19 12:32 ` Matthew Wilcox
2007-11-19 15:09 ` James Bottomley
2007-11-19 19:54 ` Benjamin Herrenschmidt
2007-11-19 19:55 ` Benjamin Herrenschmidt
2007-11-19 19:53 ` Benjamin Herrenschmidt [this message]
2007-11-19 21:43 ` Roland Dreier
2007-11-19 21:55 ` Benjamin Herrenschmidt
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=1195501984.6970.1.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rmk@arm.linux.org.uk \
/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