Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 480033

Summary: Kernel OOPS on iptables shutdown with ip_vs module loaded
Product: Red Hat Enterprise Linux 4 Reporter: Vitaly Mayatskikh <vmayatsk>
Component: kernelAssignee: Red Hat Kernel Manager <kernel-mgr>
Status: CLOSED DUPLICATE QA Contact: Martin Jenner <mjenner>
Severity: medium Docs Contact:
Priority: low    
Version: 4.8   
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-14 17:22:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vitaly Mayatskikh 2009-01-14 16:55:27 UTC
modprobe ip_vs && service iptables stop

Unable to handle kernel paging request at ffffffffa00ac9b0 RIP: 
<ffffffff80311881>{nf_unregister_sockopt+76}
PML4 103027 PGD 105027 PMD 1f9d1067 PTE 0
Oops: 0000 [1] 
CPU 0 
Modules linked in: ip_vs md5 ipv6 ip_tables button battery ac uhci_hcd 8139cp mii floppy dm_snapshot dm_zero dm_mirror ext3 jbd dm_mod
Pid: 3195, comm: modprobe Not tainted 2.6.9-78.0.8.EL
RIP: 0010:[<ffffffff80311881>] <ffffffff80311881>{nf_unregister_sockopt+76}
RSP: 0018:000001001a5abeb8  EFLAGS: 00010203
RAX: 0000000000000002 RBX: ffffffff80489960 RCX: 000000000000002e
RDX: ffffffffa00ac9a0 RSI: 000000000000006c RDI: 000001001dcd7f00
RBP: ffffffffa009d8a0 R08: 0000000000000009 R09: 0000000000000000
R10: 0000000000000048 R11: 0000000000000048 R12: 0000000000000000
R13: 0000000000000080 R14: 0000007fbffffac0 R15: 0000000000000000
FS:  0000002a9555fb00(0000) GS:ffffffff80574080(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: ffffffffa00ac9b0 CR3: 0000000000101000 CR4: 00000000000006e0
Process modprobe (pid: 3195, threadinfo 000001001a5aa000, task 000001001dfdcd20)
Stack: ffffffffa009db80 0000000000000000 ffffffffa009db80 ffffffffa009b467 
       ffffffff80452240 ffffffff8015aae0 0000000000000000 0000000000000000 
       ffffffffa009db80 ffffffff00000080 
Call Trace:<ffffffffa009b467>{:ip_tables:fini+15} <ffffffff8015aae0>{sys_delete_module+473} 
       <ffffffff80181235>{sys_munmap+94} <ffffffff80110b5a>{system_call+126} 
       

Code: 39 42 10 48 8b 17 75 21 48 8b 47 08 48 89 42 08 48 89 10 48 
RIP <ffffffff80311881>{nf_unregister_sockopt+76} RSP <000001001a5abeb8>
CR2: ffffffffa00ac9b0
 <0>Kernel panic - not syncing: Oops

Comment 1 Vitaly Mayatskikh 2009-01-14 17:04:27 UTC
Perhaps, this is candidate for 4.7.z, because latest pre-4.8 kernel (78.28) survives this scenario.

Comment 2 Vitaly Mayatskikh 2009-01-14 17:22:11 UTC

*** This bug has been marked as a duplicate of bug 456664 ***