public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: torvalds@linux-foundation.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/4] BUG_ON on kernel misbehavior on A100U2W driver
Date: Tue, 15 Jul 2008 10:17:47 -0500	[thread overview]
Message-ID: <1216135067.3312.40.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0807151012200.24544@devserv.devel.redhat.com>

On Tue, 2008-07-15 at 10:14 -0400, Mikulas Patocka wrote:
> With broken Sparc64 IOMMU accounting, the kernel submits larger requests 
> then allowed. Better to crash on BUG than corrupt memory. This needs to be 
> fixed in sparc64 code.

This analysis is correct ... and the reason we don't add driver work
arounds, so it really needs to be fixed in sparc, not worked around in
the driver.

James



  parent reply	other threads:[~2008-07-15 15:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15 14:11 [PATCH 1/4] Fix endianity in A100U2W SCSI driver Mikulas Patocka
2008-07-15 14:12 ` [PATCH 2/4] Add udelay to " Mikulas Patocka
2008-07-15 14:14   ` [PATCH 3/4] BUG_ON on kernel misbehavior on A100U2W driver Mikulas Patocka
2008-07-15 14:15     ` [PATCH 4/4] Don't crash on IOMMU overflow in " Mikulas Patocka
2008-07-15 21:19       ` Mikulas Patocka
2008-07-15 15:17     ` James Bottomley [this message]
2008-07-15 21:18     ` [PATCH 3/4] BUG_ON on kernel misbehavior on " Mikulas Patocka
2008-07-15 21:16   ` [PATCH 2/4] Add udelay to A100U2W SCSI driver Mikulas Patocka
2008-07-15 17:23 ` [PATCH 1/4] Fix endianity in " Linus Torvalds
2008-07-15 21:15   ` Mikulas Patocka

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=1216135067.3312.40.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=torvalds@linux-foundation.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