diff options
| author | Karsten Keil <kkeil@suse.de> | 2006-09-29 23:28:42 -0700 |
|---|---|---|
| committer | Jeff Garzik <jeff@garzik.org> | 2006-10-05 07:01:25 -0400 |
| commit | 39984a9fad0c642182f426d7771332d46f222103 (patch) | |
| tree | c57cec6ca1411d276fe959535b2b116167b11314 /mm | |
| parent | 0a07bc645e818b88559d99f52ad45e35352e8228 (diff) | |
| download | kernel-crypto-39984a9fad0c642182f426d7771332d46f222103.tar.gz kernel-crypto-39984a9fad0c642182f426d7771332d46f222103.tar.xz kernel-crypto-39984a9fad0c642182f426d7771332d46f222103.zip | |
[PATCH] bonding: fix deadlock on high loads in bond_alb_monitor()
In bond_alb_monitor the bond->curr_slave_lock write lock is taken
and then dev_set_promiscuity maybe called which can take some time,
depending on the network HW. If a network IRQ for this card come in
the softirq handler maybe try to deliver more packets which end up in
a request to the read lock of bond->curr_slave_lock -> deadlock.
This issue was found by a test lab during network stress tests, this patch
disable the softirq handler for this case and solved the issue.
Signed-off-by: Karsten Keil <kkeil@suse.de>
Acked-by: Jay Vosburgh <fubar@us.ibm.com>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions