linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	vegard.nossum@gmail.com, miles.lane@gmail.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-wireless@vger.kernel.org
Subject: Re: BUG: NULL pointer dereference at 00000000 -- IP: [<f8e783d5>] :b43:b43_dma_mapping_error+0x16/0x155
Date: Wed, 11 Jun 2008 07:23:32 -0500	[thread overview]
Message-ID: <484FC3C4.3070800@lwfinger.net> (raw)
In-Reply-To: <200806111205.10433.mb@bu3sch.de>

Michael Buesch wrote:
> On Wednesday 11 June 2008 02:58:44 FUJITA Tomonori wrote:
>> On Tue, 10 Jun 2008 16:50:26 +0200
>> Michael Buesch <mb@bu3sch.de> wrote:
>>
>>> On Tuesday 10 June 2008 16:42:41 Vegard Nossum wrote:
>>>> This change comes from
>>>>
>>>> commit 353c409463ecba63c3a41a992d3f5fba935eada9
>>>> Author: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
>>>> Date:   Fri May 23 19:02:30 2008 +0000
>>>
>>> Ok, FUJITA Tomonori, please make sure a patch like the following goes
>>> into the same trees that you submitted commit 353c409 to.
>>> Also make sure to check b43legacy. I _guess_ you might have added
>>> the same bug there.
>> Ah, sorry about the bug.
>>
>> From a quick look, mainline needs the same fix too?
>>
>> b43_dma_mapping_error calls unmap_descbuffer() on the failure, which
>> assumes that ring->dev is set up properly.
> 
> Yeah ok. That's an unlikely error path.
> The new bug is in the main path which will always trigger.
> 
> Next time please send _any_ patch for review to me and to the wireless list.
> Please tell me which trees this bug has been merged to. Is it already in
> Linus' tree?

The equivalent line in Linus's tree is "if 
(unlikely(dma_mapping_error(addr)))", thus the error has not reached 
mainline (yet?).

Larry


  reply	other threads:[~2008-06-11 12:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 14:09 BUG: NULL pointer dereference at 00000000 -- IP: [<f8e783d5>] :b43:b43_dma_mapping_error+0x16/0x155 Miles Lane
2008-06-10 14:23 ` Michael Buesch
2008-06-10 14:29   ` Vegard Nossum
2008-06-10 14:34     ` Michael Buesch
2008-06-10 14:37       ` Michael Buesch
2008-06-10 14:42         ` Miles Lane
2008-06-10 15:09           ` Vegard Nossum
2008-06-10 14:42         ` Vegard Nossum
2008-06-10 14:50           ` Michael Buesch
2008-06-10 22:09             ` Miles Lane
2008-06-10 22:15               ` Michael Buesch
2008-06-10 22:29                 ` Miles Lane
2008-06-10 23:15               ` Larry Finger
2008-06-11  1:57                 ` Miles Lane
2008-06-11  5:08                   ` Larry Finger
2008-06-11  5:57                     ` Miles Lane
2008-06-12  5:18                       ` FUJITA Tomonori
2008-06-11  0:58             ` FUJITA Tomonori
2008-06-11 10:05               ` Michael Buesch
2008-06-11 12:23                 ` Larry Finger [this message]
2008-06-12  5:18                 ` FUJITA Tomonori
2008-06-12  9:14                   ` Michael Buesch

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=484FC3C4.3070800@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=akpm@linux-foundation.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mb@bu3sch.de \
    --cc=miles.lane@gmail.com \
    --cc=vegard.nossum@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;
as well as URLs for NNTP newsgroup(s).