Bug 847456

Summary: BUG: unable to handle kernel NULL pointer dereference at .. tcp_finish_connect
Product: [Fedora] Fedora Reporter: Richard W.M. Jones <rjones>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, mads
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-13 13:45:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot showing stack trace none

Description Richard W.M. Jones 2012-08-11 15:30:53 UTC 
Description of problem:

Kernel crashes randomly in tcp_finish_connect.

For the full stack trace, see the attached screenshot.

Version-Release number of selected component (if applicable):

kernel-3.6.0-0.rc1.git3.2.bz844485.fc19.x86_64
(kernel-3.6.0-0.rc1.git3.2 + the 4 patches mentioned in bug 844485)

How reproducible:

Twice already.

Steps to Reproduce:
1. Do stuff, crashes randomly.

This email seems relevant:
http://www.spinics.net/lists/netdev/msg207318.html
Comment 1 Richard W.M. Jones 2012-08-11 15:43:05 UTC 
Created attachment 603695 [details]
screenshot showing stack trace

tcp_finish_connect
tcp_rcv_state_process
sched_clock
native_sched_clock
tcp_v4_do_rcv
release_sock
__inet_stream_connect
trace_hardirqs_on
wake_up_bit
inet_stream_connect
inet_stream_connect
sys_connect
Comment 2 Richard W.M. Jones 2012-08-11 15:43:38 UTC 
FYI I am building and testing a kernel that contains
the patch from comment 0.
Comment 3 Richard W.M. Jones 2012-08-11 16:34:37 UTC 
The patch mentioned in the email in comment 0 does appear
to fix the problem, so far.
Comment 4 Richard W.M. Jones 2012-08-11 18:31:59 UTC 
Been running for ~2 hours without crashing, whereas before
applying the patch it ran for about 5 mins.
Comment 5 Richard W.M. Jones 2012-08-12 20:14:21 UTC 
My uptime is now just over a day:

$ uptime
 21:13:54 up 1 day,  3:47,  2 users,  load average: 0.00, 0.01, 0.05

So I think I can say that the patch works ...
Comment 6 Josh Boyer 2012-08-13 13:45:26 UTC 
That patch got sucked in through patch-3.6-rc1-git5.xz today.  Should be fixed in tomorrow's f18/rawhide.

Thanks for the report.
Comment 7 Mads Kiilerich 2012-08-13 15:47:45 UTC 
I confirm that 3.6.0-0.rc1.git5.1.fc18.x86_64 is substantially better in this area.