diff options
| author |   Alexandra Winter <wintera@linux.ibm.com> | 2019-12-23 15:03:24 +0100 |
|---|---|---|
| committer |   David S. Miller <davem@davemloft.net> | 2019-12-24 22:41:06 -0800 |
| commit | e8a66d800471e2df7f0b484e2e46898b21d1fa82 (patch) | |
| tree | 732b36f28e64e2fa813febe031310ba698b66f5d /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | s390/qeth: fix false reporting of VNIC CHAR config failure (diff) | |
| download | wireguard-linux-e8a66d800471e2df7f0b484e2e46898b21d1fa82.tar.xz wireguard-linux-e8a66d800471e2df7f0b484e2e46898b21d1fa82.zip | |
s390/qeth: Fix vnicc_is_in_use if rx_bcast not set
Symptom: After vnicc/rx_bcast has been manually set to 0,
bridge_* sysfs parameters can still be set or written.
Only occurs on HiperSockets, as OSA doesn't support changing rx_bcast.
Vnic characteristics and bridgeport settings are mutually exclusive.
rx_bcast defaults to 1, so manually setting it to 0 should disable
bridge_* parameters.
Instead it makes sense here to check the supported mask. If the card
does not support vnicc at all, bridge commands are always allowed.
Fixes: caa1f0b10d18 ("s390/qeth: add VNICC enable/disable support")
Signed-off-by: Alexandra Winter <wintera@linux.ibm.com>
Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions