From: "Miles Lane" <miles.lane@gmail.com>
To: "Michael Buesch" <mb@bu3sch.de>
Cc: "Vegard Nossum" <vegard.nossum@gmail.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: BUG: NULL pointer dereference at 00000000 -- IP: [<f8e783d5>] :b43:b43_dma_mapping_error+0x16/0x155
Date: Tue, 10 Jun 2008 10:42:38 -0400 [thread overview]
Message-ID: <a44ae5cd0806100742t1bd275dib43c5d72b3dd9659@mail.gmail.com> (raw)
In-Reply-To: <200806101637.11473.mb@bu3sch.de>
Sorry, I forgot to label the kernel tree. It is 2.6.26-rc5-mm2.
On Tue, Jun 10, 2008 at 10:37 AM, Michael Buesch <mb@bu3sch.de> wrote:
> On Tuesday 10 June 2008 16:34:21 Michael Buesch wrote:
>> On Tuesday 10 June 2008 16:29:17 Vegard Nossum wrote:
>> > On Tue, Jun 10, 2008 at 4:23 PM, Michael Buesch <mb@bu3sch.de> wrote:
>> > > On Tuesday 10 June 2008 16:09:37 Miles Lane wrote:
>> > >> BUG: unable to handle kernel NULL pointer dereference at 00000000
>> > >> IP: [<f8e783d5>] :b43:b43_dma_mapping_error+0x16/0x155
>> > >
>> > >
>> > > It seems to crash at
>> > > 60 extern const struct dma_mapping_ops *dma_ops;
>> > > 61
>> > > 62 static inline int dma_mapping_error(dma_addr_t dma_addr)
>> > > 63 {
>> > > 64 if (dma_ops->mapping_error)
>> > > 65 return dma_ops->mapping_error(dma_addr);
>> > > 66
>> > > 67 return (dma_addr == bad_dma_address);
>> > > 68 }
>> >
>> > No, this is wrong.
>> >
>> > /* Check if a DMA mapping address is invalid. */
>> > static bool b43_dma_mapping_error(struct b43_dmaring *ring,
>> > dma_addr_t addr,
>> > size_t buffersize, bool dma_to_device)
>> > {
>> > if (unlikely(dma_mapping_error(ring->dev->dev->dma_dev, addr)))
>> >
>> > It crashes on this line ---^
>>
>> Which calls dma_mapping_error(), correct?
>>
>> But you are right. I see the bug now.
>> ring->dev is assigned after the call.
>> I wonder why it works reliably on all of my machines.
>>
>
> Ehm no wait a second...
> What strange tree are you looking at?
> This is a copy of the code from my local tree.
>
> 516 /* Check if a DMA mapping address is invalid. */
> 517 static bool b43_dma_mapping_error(struct b43_dmaring *ring,
> 518 dma_addr_t addr,
> 519 size_t buffersize, bool dma_to_device)
> 520 {
> 521 if (unlikely(dma_mapping_error(addr)))
> 522 return 1;
>
> This code is perfectly fine.
> This must be some merge error in some upstream tree.
>
> --
> Greetings Michael.
>
next prev parent reply other threads:[~2008-06-10 14:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 14:09 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 [this message]
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
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=a44ae5cd0806100742t1bd275dib43c5d72b3dd9659@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--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
Powered by JetHome