From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 73011] New: Kernel Panic
Date: Thu, 27 Mar 2014 09:01:44 -0700 [thread overview]
Message-ID: <20140327090144.32409a75@samsung-9> (raw)
Begin forwarded message:
Date: Thu, 27 Mar 2014 03:15:20 -0700
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 73011] New: Kernel Panic
https://bugzilla.kernel.org/show_bug.cgi?id=73011
Bug ID: 73011
Summary: Kernel Panic
Product: Networking
Version: 2.5
Kernel Version: 3.4
Hardware: ARM
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: IPV4
Assignee: shemminger@linux-foundation.org
Reporter: vijayborqs1982@gmail.com
Regression: No
Unable to handle kernel NULL pointer dereference at virtual address 000000c8
pgd = ec990000
[000000c8] *pgd=00000000
Internal error: Oops: 5 [#1] PREEMPT SMP ARM
CPU: 1 Tainted: G W (3.4.0-liberty)
PC is at __ip_route_output_key+0x49c/0x798
LR is at inet_select_addr+0xf8/0x104
pc : <c0709654> lr : <c0735fc4> psr: 20030013
sp : eca97c28 ip : 00000001 fp : 012ba8c0
r10: 00000000 r9 : 00000000 r8 : c11dcd00
r7 : 00000000 r6 : 00000000 r5 : 00000000 r4 : eca97cd4
r3 : ebe22100 r2 : ec0c0000 r1 : c11dccd8 r0 : 00000000
Flags: nzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user
Control: 10c5787d Table: ad39006a DAC: 00000015
..
Faulting Process ping (pid: 6719, stack limit = 0xeca962f0)
...
Call Stack
Kernel Panic in this func __ip_route_output_key()
====>ip_route_output_flow()
===>ping_v4_sendmsg()
===>inet_sendmsg()
===>sock_sendmsg()
===>__sys_sendmsg()
===>sys_sendmsg()
kernel/net/ipv4/route.c
***********************
dev_out = FIB_RES_DEV(res);
fl4->flowi4_oif = dev_out->ifindex;
***********************
dev_out looks like NULL. When dev_out is accessed it is resulting in NULL Ptr
Def and finally Kernel Panic.
Any experts who can fix this issue. It is very rarely reproduced on ARM 32-bit
ARCH.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2014-03-27 16:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140327090144.32409a75@samsung-9 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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