diff options
| author | Marcelo Ricardo Leitner <marcelo.leitner@gmail.com> | 2015-12-04 18:14:04 +0100 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-12-06 04:23:22 +0100 |
| commit | 01ce63c90170283a9855d1db4fe81934dddce648 (patch) | |
| tree | eab8388f522d7f71c2e96b343370ac50f6ff64d8 /include/trace | |
| parent | sctp: use the same clock as if sock source timestamps were on (diff) | |
| download | linux-01ce63c90170283a9855d1db4fe81934dddce648.tar.xz linux-01ce63c90170283a9855d1db4fe81934dddce648.zip | |
sctp: update the netstamp_needed counter when copying sockets
Dmitry Vyukov reported that SCTP was triggering a WARN on socket destroy
related to disabling sock timestamp.
When SCTP accepts an association or peel one off, it copies sock flags
but forgot to call net_enable_timestamp() if a packet timestamping flag
was copied, leading to extra calls to net_disable_timestamp() whenever
such clones were closed.
The fix is to call net_enable_timestamp() whenever we copy a sock with
that flag on, like tcp does.
Reported-by: Dmitry Vyukov <dvyukov@google.com>
Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Acked-by: Vlad Yasevich <vyasevich@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/trace')
0 files changed, 0 insertions, 0 deletions