On Thu, Sep 24, 2020 at 3:01 AM David Miller wrote:
>
> From: Hauke Mehrtens
> Date: Tue, 22 Sep 2020 23:41:12 +0200
>
> > The TX DMA channel data is accessed by the xrx200_start_xmit() and the
> > xrx200_tx_housekeeping() function from different threads. Make sure the
> > accesses are synchroniz
On 9/24/20 3:01 AM, David Miller wrote:
> From: Hauke Mehrtens
> Date: Tue, 22 Sep 2020 23:41:12 +0200
>
>> The TX DMA channel data is accessed by the xrx200_start_xmit() and the
>> xrx200_tx_housekeeping() function from different threads. Make sure the
>> accesses are synchronized by acquiring t
On Thu, Sep 24, 2020 at 3:01 AM David Miller wrote:
>
> From: Hauke Mehrtens
> Date: Tue, 22 Sep 2020 23:41:12 +0200
>
> > The TX DMA channel data is accessed by the xrx200_start_xmit() and the
> > xrx200_tx_housekeeping() function from different threads. Make sure the
> > accesses are synchroniz
From: Hauke Mehrtens
Date: Tue, 22 Sep 2020 23:41:12 +0200
> The TX DMA channel data is accessed by the xrx200_start_xmit() and the
> xrx200_tx_housekeeping() function from different threads. Make sure the
> accesses are synchronized by acquiring the netif_tx_lock() in the
> xrx200_tx_housekeepin
The TX DMA channel data is accessed by the xrx200_start_xmit() and the
xrx200_tx_housekeeping() function from different threads. Make sure the
accesses are synchronized by acquiring the netif_tx_lock() in the
xrx200_tx_housekeeping() function too. This lock is acquired by the
kernel before calling