From: Michael Buesch <mb@bu3sch.de>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: 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: Thu, 12 Jun 2008 11:14:53 +0200 [thread overview]
Message-ID: <200806121114.54445.mb@bu3sch.de> (raw)
In-Reply-To: <20080612142235A.fujita.tomonori@lab.ntt.co.jp>
On Thursday 12 June 2008 07:18:32 FUJITA Tomonori wrote:
> > Yeah ok. That's an unlikely error path.
>
> Yeah, it doesn't always happen, but it possible that it happens?
Yes. I will create a new patch and send it to John Linville.
So it will also quickly end up in the -mm tree, too.
This will fix both bugs.
> No, seems that there are some confusion. This is just in -mm to find
> problems:
>
> http://userweb.kernel.org/~akpm/mmotm/broken-out/dma-mapping-add-the-device-argument-to-dma_mapping_error.patch
>
> This patch is a trivial but changes lots of places. So it's difficult
> to get an ACK on all the places.
Thanks a lot for explaining this. This makes things a lot easier.
> This patch need several fixes but all the patches are trivial except
> for b34. I guess that it is because b34 handles devices for
It's called b43 ;)
> dma-mapping in an uncommon way.
Yeah, the hardware is pretty stupid, so we have lots of special workarounds
and so on... So I hardly touch the DMA code and was very surprised about
this bugreport. :)
--
Greetings Michael.
prev parent reply other threads:[~2008-06-12 9:15 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
2008-06-12 5:18 ` FUJITA Tomonori
2008-06-12 9:14 ` Michael Buesch [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=200806121114.54445.mb@bu3sch.de \
--to=mb@bu3sch.de \
--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=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 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.