From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: dmabounce: fix dmabounce may cause crash issue
Date: Fri, 25 Mar 2011 08:36:30 +0000 [thread overview]
Message-ID: <20110325083630.GA26481@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1300965400-28304-1-git-send-email-b29396@freescale.com>
On Thu, Mar 24, 2011 at 07:16:40PM +0800, Aisheng.Dong wrote:
> The map_single does not check if dev is NULL which may cause kernel panic
> like follows:
> Unable to handle kernel NULL pointer dereference at virtual address 000000bc
> pgd = 80004000
> [000000bc] *pgd=00000000
> Internal error: Oops: 5 [#1] PREEMPT
> last sysfs file:
> Modules linked in:
> CPU: 0 Not tainted (2.6.35.3-00845-g204c152-dirty #112)
> PC is at dma_map_single+0x2c/0x2a0
> LR is at fec_enet_interrupt+0x1d4/0x450
> pc : [<8003cf04>] lr : [<802936b8>] psr: 60000193
> sp : 80809ec8 ip : 00000080 fp : 99308040
> r10: 99308040 r9 : 00000002 r8 : 99074f00
> r7 : fa0a5000 r6 : 00000000 r5 : 00000060 r4 : 992e4000
> r3 : 00000002 r2 : 8080cac0 r1 : 99308040 r0 : 00000000
>
> The patch checks the dev to avoid this issue and align with the
> original dma_map_single to allow dev is NULL.
Is there a reason that the FEC code can't pass the appropriate struct
device?
next prev parent reply other threads:[~2011-03-25 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 11:16 [PATCH 1/1] ARM: dmabounce: fix dmabounce may cause crash issue Aisheng.Dong
2011-03-24 13:56 ` Mikael Pettersson
2011-03-28 4:48 ` Dong Aisheng-B29396
2011-03-25 8:36 ` Russell King - ARM Linux [this message]
2011-03-28 5:01 ` Dong Aisheng-B29396
2011-03-28 17:58 ` Russell King - ARM Linux
2011-03-29 3:04 ` Dong Aisheng-B29396
2011-03-30 10:53 ` Dong Aisheng-B29396
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=20110325083630.GA26481@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/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).