Bug 1272571
| Summary: | Kernel 4.2.3-200 oopses when I bring up a GRE tunnel inside IPSec [also 4.2.5-201] | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Chris Siebenmann <cks-rhbugzilla> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 22 | CC: | gansalmon, itamar, jforbes, jhenner, jonathan, kafai, kernel-maint, madhu.chinakonda, mchehab, steved | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | kernel-4.2.6-301.fc23 kernel-4.2.6-201.fc22 | Doc Type: | Bug Fix | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-11-26 20:55:36 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
Chris Siebenmann
2015-10-16 19:06:40 UTC
I have now captured a full OOPS from a Fedora 22 virtual machine's virtual serial console. I'll attach it here. Created attachment 1088662 [details]
Full serial console OOPS from a Fedora 22 virtual machine
This OOPS is slightly different to what I see on my workstation, but it
happens in exactly the same way as before.
Created attachment 1089920 [details]
Fedora 23 kernel OOPS from a virtual machine
Unsurprisingly, this issue reproduces on Fedora 23 as well. I've attached
a captured kernel oops from a virtual machine. This oops looks more like
my initial one, so perhaps there are multiple places where this bug can
happen.
Created attachment 1090296 [details]
Serial console OOPS from Fedora 22 with kernel 4.2.5-201
I tried this again in the just released 4.2.5-201 kernel and it paniced
as before. I've attached the serial console log.
Seeing same issue here with similar dump. Because of lack of serial console can't check it, but here it is not GRE tunnelling as per Chris; my solution (by elimination) was disabling radvd which allowed boot with full stack including two VPN tunnels and an IPV6 tunnel loaded. I built a stock 4.2.5 kernel from kernel.org (but reusing the Fedora 22 config) and then a stock 4.3 kernel, and this issue is present in both of them. I'll see if I can bisect this in the upstream kernel source but this may take some time. It appears that this bug may already be recognized upstream in the kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=106611 This report fingers git commit 8d0b94afdca84598912347e61defa846a0988d04. I have not tested this myself. Thanks for the report. I manage to report now. I will work on a patch. This one (gre over ipsec) should be different from the upstream bug #106611 which should have been fixed in 4.3 by: ebfa45f ipv6: Move common init code for rt6_info to a new function rt6_info_init() 0a1f596 ipv6: Initialize rt6_info properly in ip6_blackhole_route() typo: I meant I managed to reproduce it now. For the record/people following this bug: this issue is not fixed in the just-released Fedora 22 update kernel 4.2.6-200.fc22. It does seem to be fixed by the upstream commit 0d3f6d297bfb7af24d0508460fdb3d1ec4903fa3 that Martin KaFai Lau made. This patch is added in git and queued for the next F22/23 builds. kernel-4.2.6-301.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-f26dec73e9 kernel-4.2.6-201.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-912d8e4998 kernel-4.2.6-201.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update kernel' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-912d8e4998 kernel-4.2.6-301.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update kernel' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-f26dec73e9 kernel-4.2.6-301.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 1286471 has been marked as a duplicate of this bug. *** kernel-4.2.6-201.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. It seems like this is not 100% reproducible, but I was able to reproduce with #sudo ip tun add server mode gre remote `resolveip -s xxx.eng.bos.redhat.com` local A.B.C.D ttl 255 #sudo firewall-cmd --direct --add-rule ipv4 filter INPUT 0 -p gre -j ACCEPT success #sudo ip a a 172.25.1.2/30 dev server #sudo ip l s server up several times. I have just installed the newer kernel. I will watch it. |