summaryrefslogtreecommitdiffstats
path: root/security/keys/keyring.c
diff options
context:
space:
mode:
authorJulian Wiedmann <jwi@linux.ibm.com>2018-09-17 17:36:06 +0200
committerDavid S. Miller <davem@davemloft.net>2018-09-17 18:10:25 +0200
commit4d19db777a2f32c9b76f6fd517ed8960576cb43e (patch)
treeeb5c42a655c80f5ac6300f487866004415c02e26 /security/keys/keyring.c
parents390/qeth: uninstall IRQ handler on device removal (diff)
downloadlinux-4d19db777a2f32c9b76f6fd517ed8960576cb43e.tar.xz
linux-4d19db777a2f32c9b76f6fd517ed8960576cb43e.zip
s390/qeth: invoke softirqs after napi_schedule()
Calling napi_schedule() from process context does not ensure that the NET_RX softirq is run in a timely fashion. So trigger it manually. This is no big issue with current code. A call to ndo_open() is usually followed by a ndo_set_rx_mode() call, and for qeth this contains a spin_unlock_bh(). Except for OSN, where qeth_l2_set_rx_mode() bails out early. Nevertheless it's best to not depend on this behaviour, and just fix the issue at its source like all other drivers do. For instance see commit 83a0c6e58901 ("i40e: Invoke softirqs after napi_reschedule"). Fixes: a1c3ed4c9ca0 ("qeth: NAPI support for l2 and l3 discipline") Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'security/keys/keyring.c')
0 files changed, 0 insertions, 0 deletions