Revision 0f399305cd31e5c813086eaa264f7f47e205c10e authored by Julian Wiedmann on 18 December 2019, 15:32:27 UTC, committed by David S. Miller on 21 December 2019, 05:00:27 UTC
When managing the promiscuous mode during an RX modeset, qeth caches the
current HW state to avoid repeated programming of the same state on each
modeset.

But while tearing down a device, we forget to clear the cached state. So
when the device is later set online again, the initial RX modeset
doesn't program the promiscuous mode since we believe it is already
enabled.
Fix this by clearing the cached state in the tear-down path.

Note that for the SBP variant of promiscuous mode, this accidentally
works right now because we unconditionally restore the SBP role while
re-initializing.

Fixes: 4a71df50047f ("qeth: new qeth device driver")
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Reviewed-by: Alexandra Winter <wintera@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
1 parent 2e3d7fa
History
File Mode Size
Kconfig -rw-r--r-- 1.3 KB
Makefile -rw-r--r-- 218 bytes
xz_crc32.c -rw-r--r-- 1.2 KB
xz_dec_bcj.c -rw-r--r-- 13.6 KB
xz_dec_lzma2.c -rw-r--r-- 28.5 KB
xz_dec_stream.c -rw-r--r-- 19.4 KB
xz_dec_syms.c -rw-r--r-- 664 bytes
xz_dec_test.c -rw-r--r-- 5.2 KB
xz_lzma2.h -rw-r--r-- 6.0 KB
xz_private.h -rw-r--r-- 4.5 KB
xz_stream.h -rw-r--r-- 1.4 KB

back to top