Our customer experienced a kernel panic after a kernel upgrade on the node boot stage.
Kernel panic calltrace (process - 'modprobe'):
The affected kernel is based on 2.6.18-194.3.1.el5.
Checking the code:
destroy_workqueue() is called in bonding_init() on err path AND in bond_destructor() one after another.
This issue has been already fixed in mainstream:
bonding: fix panic if initialization fails
If module initialisation failed (e.g. because the bonding sysfs entry
cannot be created), kernel panics:
IP: [<ffffffff8024910a>] destroy_workqueue+0x2d/0x146
Remove the calls to bond_work_cancel_all() and destroy_workqueue();
both are also called/scheduled via bond_free_all().
bond_destroy_sysfs is unecessary because the sysfs entry has
not been created in the error case.
Signed-off-by: Florian Westphal <firstname.lastname@example.org>
Signed-off-by: Jay Vosburgh <email@example.com>
Signed-off-by: Jiri Pirko <firstname.lastname@example.org>
Signed-off-by: David S. Miller <email@example.com>
Please, apply the patch too.
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
Patch(es) available in kernel-2.6.18-284.el5
You can download this test kernel (or newer) from http://people.redhat.com/jwilson/el5
Detailed testing feedback is always welcomed.
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.