public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: 王神 <oujin.rera@gmail.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: dma_mask on scsi_calculate_bounce_limit
Date: Fri, 19 Nov 2010 09:15:40 -0600	[thread overview]
Message-ID: <1290179740.23556.13.camel@mulgrave.site> (raw)
In-Reply-To: <AANLkTimb6iHPTUCco+stpPCGZJUGC3ePBTik6=GOaa6H@mail.gmail.com>

On Fri, 2010-11-19 at 12:11 +0530, 王神 wrote:
> On Fri, Nov 19, 2010 at 6:22 AM, James Bottomley
> <James.Bottomley@suse.de> wrote:
> > On Fri, 2010-11-19 at 01:54 +0800, 王神 wrote:
> >> On Thu, Nov 18, 2010 at 11:21 PM, James Bottomley
> >> <James.Bottomley@suse.de> wrote:
> >> > On Thu, 2010-11-18 at 14:20 +0530, 王神 wrote:
> >> >> Hi
> >> >>
> >> >> I have enabled DMA for my host device and when i connect a scsi device
> >> >> to the host, it crashes in the following code..
> >> >>
> >> >> Function: scsi_calculate_bounce_limit
> >> >>
> >> >>  if (host_dev && host_dev->dma_mask)
> >> >>                 bounce_limit = *host_dev->dma_mask;
> >> >>
> >> >> "*dma_mask" is illegal pointer operation. I would like to understand
> >> >> is this known and is there reason behind such a code ?
> >> >
> >> > It likely means you're operating on a new architecture and its generic
> >> > devices haven't been set up correctly.
> >>
> >> Could you please more specific on what is generic devices haven't been
> >> setup properly...
> >
> > It means the architecture setup code left a NULL pointer in the generic
> > device which shouldn't be there ... without knowing which architecture
> > and seeing the code, it's pretty impossible to be more specific.
> 
> It is for ARM and the error is not due to NULL pointer. The code just
> checks if it is host mode + dma enabled and it access a normal
> interger variable with indirection causing the crash;

OK, it's crashing because the pointer isn't set up correctly ... is that
more semantically accurate?

The pointer setup is done in the arch code, so that's where the problem
is.

> int dma_mask;

That's not the definition in struct device; this is:

        u64             *dma_mask;      /* dma mask (if dma'able device) */


> and accessing dma_mask as "*dma_mask" ??
> 
> Anything I am missing :O

Yes, but you supply too little information to know what.  It's
definitely a problem somewhere in the arch setup code.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-11-19 15:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18  8:50 dma_mask on scsi_calculate_bounce_limit 王神
2010-11-18 15:21 ` James Bottomley
2010-11-18 17:54   ` 王神
2010-11-19  0:52     ` James Bottomley
2010-11-19  6:41       ` 王神
2010-11-19 15:13         ` Douglas Gilbert
2010-11-19 15:15         ` James Bottomley [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=1290179740.23556.13.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=oujin.rera@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