Red Hat Bugzilla – Bug 627958
be2net: A bad assert in processing async messages from NIC
Last modified: 2011-05-19 08:38:37 EDT
An unexpected message received from NIC could cause a crash due to a stale assert. This should be removed.
Created attachment 441527 [details] Patch to remove a bad assert Async notifications other than link status are possible in certain configurations. Remove the BUG_ON in the mcc completion processing path. This patch has been submitted upstream Subbu
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
Patch(es) available on kernel-2.6.32-83.el6
Hi, do you have any idea of how to produce the bad assert to reproduce the bug & verifying?
I cant think of any way to reproduce the problem.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0542.html