Bug 196529
| Summary: | NULL pointer deref in networking | ||
|---|---|---|---|
| Product: | Networking | Reporter: | Rafael Cepeda (rcepeda1993) |
| Component: | Other | Assignee: | Stephen Hemminger (stephen) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | regressions |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 4.13rc2 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: | dmesg output | ||
FYI: This issues is tracked in the regression reports for Linux 4.13 (http://bit.ly/lnxregrep413 ) with this id: Linux-Regression-ID: lr#084be9 Please include this line in the comment section of patches that are supposed to fix the issue. Please also mention the string once in other mailinglist threads or different bug tracking entries if you or someone else start to discuss the issue there. By including that string you make it a whole lot easier to track where an issue gets discussed and how far patches to fix it have made it. More details on this: http://bit.ly/lnxregtrackid Thx for your help. FYI: most network developers afaik don't use bugzilla.kernel.org; you might better off sending your report to netdev instead: https://www.kernel.org/doc/Documentation/networking/netdev-FAQ.txt Is the issue still present? Did you forward it to netdev? I didn't find it. Side note: I'll remove the issue from the regression reports in a week from now to prevent it getting filled with stalled reports. Thorsten, I apologize, I misunderstood you on forwarding the ticket to netdev. I thought you were educating me about netdev, and that you would submit it in the reports. The issue still occurs; even after trying out rc3. I will submit a ticket to netdev now, thanks. (In reply to Rafael Cepeda from comment #4) > Thorsten, I apologize, No worries > The issue still occurs; even after trying out rc3. Note: better try rc4, as there was a bunch of changes in the network code just after rc3 > I will submit a ticket to netdev now, thanks. thx! Thorsten, thanks to your recommendation, I tried out rc4 and it works! What should I do regarding my netdev ticket? I am sure commit aae4e7a8bc fixed the issue. It is my NIC and the change is trivial. |
Created attachment 257749 [details] 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.