forked from Minki/linux
wimax/i2400m: don't call netif_start_queue() in _tx_msg_sent()
Reported and fixed by Cindy H Kao. When the device is stopped __i2400m_dev_stop() stops the network queue. However, when this is done in the middle of heavy network operation, when the bus-specific subdriver is still wrapping up and it reports a sent TX transaction with _tx_msg_sent() right after the device was stopped, the queue was being started again, which was causing a stream of oopsen and finally a panic. In any case, said call has no place there. It's a left over from an early implementation that was discarded later on. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
This commit is contained in:
parent
fb10167478
commit
fff1068559
@ -773,7 +773,6 @@ void i2400m_tx_msg_sent(struct i2400m *i2400m)
|
||||
n = i2400m->tx_out / I2400M_TX_BUF_SIZE;
|
||||
i2400m->tx_out %= I2400M_TX_BUF_SIZE;
|
||||
i2400m->tx_in -= n * I2400M_TX_BUF_SIZE;
|
||||
netif_start_queue(i2400m->wimax_dev.net_dev);
|
||||
spin_unlock_irqrestore(&i2400m->tx_lock, flags);
|
||||
d_fnend(3, dev, "(i2400m %p) = void\n", i2400m);
|
||||
}
|
||||
|
Loading…
Reference in New Issue
Block a user