RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 851874 - networking halts when mirred target device disappears
Summary: networking halts when mirred target device disappears
Keywords:
Status: CLOSED DUPLICATE of bug 846585
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-26 19:36 UTC by Dan Kenigsberg
Modified: 2012-08-27 11:27 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-27 11:27:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dan Kenigsberg 2012-08-26 19:36:50 UTC
Description of problem:
Host is configured with eth0 connected to a bridge, the latter carrying an IP address. tc ingress rules on the bridge mirror all IP traffic to the tap device associated with a vNIC of qemu-kvm guest.

When qemu dies, the tap device is removed, and host connectivity is lost.

On 08/15/2012 09:25 AM, Jason Wang wrote:
> Unfortunately, current kernel would drop packet when the mirred device
> is removed. It depends on the management to do the correct configuration
> to make things work I think. Vdsm or other mgmt should take care of the
> filter configuration. Maybe we can change the behavior but I'm not sure
> whether or not it would break anything.

Version-Release number of selected component (if applicable):
2.6.32-279.5.2.el6.x86_64

How reproducible:
Ask Genadi for exact probability.

Steps to Reproduce:
- brctl addbr ovirtmgmt
- brctl addif ovirtmgmt eth0
- ifconfig ovirtmgmt host.ip.add.ress
- start qemu with a tap device called vnet0
- /sbin/tc qdisc add dev ovirtmgmt ingress
- /sbin/tc filter add dev ovirtmgmt parent ffff: protocol ip u32 match u8 0 0 action mirred egress mirror dev vnet0
- /sbin/tc qdisc add dev ovirtmgmt parent root prio
- /sbin/tc qdisc show dev ovirtmgmt
- /sbin/tc filter add dev ovirtmgmt parent <prio_qdisc_id>: protocol ip u32 match u8 0 0 action mirred egress mirror dev vnet0

traffic is now mirred into the VM.

- kill the VM (may happen due to qemu bugs)

Actual results:
- host looses connectivity

Expected results:
- host continues to see incoming traffic. Filter to a no-longer-existing device is ignored, not blocking packets.


Note You need to log in before you can comment on or make changes to this bug.