Cannot reproduce; what are the exact steps to reproduce on (pure) RHEL? Any bridges involved, etc.? What kernel version was used to capture the trace in attachment 587619 [details]?
Hmm, never mind, 3b410a310b48a8e7de3438957635093596ad5ca5 fixes this bug. If you could still describe the setup used to reproduce this, it would be nice.
(In reply to comment #3) > Hmm, never mind, 3b410a310b48a8e7de3438957635093596ad5ca5 fixes this bug. In what tree can I find this commit? > If you could still describe the setup used to reproduce this, it would be > nice. It is a plain RHEL system (VM) with kernel 2.6.32-279 and a bridge with one slave device. Do you need more details?
(In reply to comment #4) > In what tree can I find this commit? Upstream vanilla, I'm backporting and testing the patch now. > It is a plain RHEL system (VM) with kernel 2.6.32-279 and a bridge with one > slave device. > Do you need more details? No, seems that I reproduced it. Thanks!
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Patch(es) available on kernel-2.6.32-294.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0496.html