All of lore.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dgilbert@interlog.com>
To: 王神 <oujin.rera@gmail.com>
Cc: James Bottomley <James.Bottomley@suse.de>, linux-scsi@vger.kernel.org
Subject: Re: dma_mask on scsi_calculate_bounce_limit
Date: Fri, 19 Nov 2010 10:13:29 -0500	[thread overview]
Message-ID: <4CE69419.2020201@interlog.com> (raw)
In-Reply-To: <AANLkTimb6iHPTUCco+stpPCGZJUGC3ePBTik6=GOaa6H@mail.gmail.com>

On 10-11-19 01:41 AM, 王神 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;
> 
> int dma_mask;
> 
> and accessing dma_mask as "*dma_mask" ??
> 
> Anything I am missing :O

Yes, supplying more information.

I'm familiar with AT91SAM9G20 which is an ARM based
microcontroller. The directory of interest in the kernel
source is arch/arm/mach-at91 and for the G20 the
at91sam9260_devices.c file defines its DMA masks for
its devices. In all cases that I can see the dma_mask is
the address of a u64 holding DMA_BIT_MASK(32) .

There are no real SCSI devices on the G20 but USB
might be regarded as SCSI "once removed". And the
USB devices on the G20 have dma_mask values as
described above.

Doug Gilbert

--
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

  reply	other threads:[~2010-11-19 15:13 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 [this message]
2010-11-19 15:15         ` James Bottomley

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=4CE69419.2020201@interlog.com \
    --to=dgilbert@interlog.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.