From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 196529] New: NULL pointer deref in networking
Date: Sat, 29 Jul 2017 14:33:20 -0700 [thread overview]
Message-ID: <20170729143320.347eb4d1@xeon-e3> (raw)
Begin forwarded message:
Date: Sat, 29 Jul 2017 01:52:42 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 196529] New: NULL pointer deref in networking
https://bugzilla.kernel.org/show_bug.cgi?id=196529
Bug ID: 196529
Summary: NULL pointer deref in networking
Product: Networking
Version: 2.5
Kernel Version: 4.13rc2
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: stephen@networkplumber.org
Reporter: rcepeda1993@gmail.com
Regression: No
Created attachment 257749
--> https://bugzilla.kernel.org/attachment.cgi?id=257749&action=edit
dmesg output
Just upgraded to 4.13rc2, rebooted, and my system crashed at my netmount init
script; says RIP is NULL, I am guessing a bad func call. I immediately thought
missing firmware in kernel, my kernel builds firmware in it, so I upgraded my
firmware to latest on git.kernel and made sure I had no warnings in dmesg about
missing firmware. Still, I receive this NULL pointer in the IP. If I disable my
netmount on boot, I can login, but can not bring up my interfaces, still get a
RIP err in kernel logs and cpu load sky-rockets.
I am willing to help and provide as much info as possible, thank you.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2017-07-29 21:33 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=20170729143320.347eb4d1@xeon-e3 \
--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