diff options
| author | Eric Dumazet <edumazet@google.com> | 2017-03-01 22:28:39 (GMT) |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-03-22 11:43:32 (GMT) |
| commit | 3d87dce3dfd665a892d107b797e68697204c3e43 (patch) | |
| tree | e0110d523117321e125396228a462f03c3df0806 /net/rose | |
| parent | 62fe0521fb6cc3b887fdc00ddca9c38d2614b8b0 (diff) | |
| download | linux-3d87dce3dfd665a892d107b797e68697204c3e43.tar.xz | |
net: net_enable_timestamp() can be called from irq contexts
[ Upstream commit 13baa00ad01bb3a9f893e3a08cbc2d072fc0c15d ]
It is now very clear that silly TCP listeners might play with
enabling/disabling timestamping while new children are added
to their accept queue.
Meaning net_enable_timestamp() can be called from BH context
while current state of the static key is not enabled.
Lets play safe and allow all contexts.
The work queue is scheduled only under the problematic cases,
which are the static key enable/disable transition, to not slow down
critical paths.
This extends and improves what we did in commit 5fa8bbda38c6 ("net: use
a work queue to defer net_disable_timestamp() work")
Fixes: b90e5794c5bd ("net: dont call jump_label_dec from irq context")
Signed-off-by: Eric Dumazet <edumazet@google.com>
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/rose')
0 files changed, 0 insertions, 0 deletions