Xin Long 220f0f866d sctp: update hb timer immediately after users change hb_interval ... [ Upstream commit 1f4e803cd9 ] Currently, when hb_interval is changed by users, it won't take effect until the next expiry of hb timer. As the default value is 30s, users have to wait up to 30s to wait its hb_interval update to work. This becomes pretty bad in containers where a much smaller value is usually set on hb_interval. This patch improves it by resetting the hb timer immediately once the value of hb_interval is updated by users. Note that we don't address the already existing 'problem' when sending a heartbeat 'on demand' if one hb has just been sent(from the timer) mentioned in: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg590224.html Signed-off-by: Xin Long <lucien.xin@gmail.com> Reviewed-by: Simon Horman <horms@kernel.org> Fixes: 1da177e4c3 ("Linux-2.6.12-rc2") Link: https://lore.kernel.org/r/75465785f8ee5df2fb3acdca9b8fafdc18984098.1696172660.git.lucien.xin@gmail.com Signed-off-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: Sasha Levin <sashal@kernel.org>		2023-10-10 22:00:44 +02:00
..
Kconfig	…
Makefile	…
associola.c	…
auth.c	…
bind_addr.c	…
chunk.c	…
debug.c	…
diag.c	…
endpointola.c	…
input.c	…
inqueue.c	…
ipv6.c	…
objcnt.c	…
offload.c	…
output.c	…
outqueue.c	…
primitive.c	…
proc.c	…
protocol.c	…
sm_make_chunk.c	…
sm_sideeffect.c	…
sm_statefuns.c	…
sm_statetable.c	…
socket.c	sctp: update hb timer immediately after users change hb_interval	2023-10-10 22:00:44 +02:00
stream.c	…
stream_interleave.c	…
stream_sched.c	…
stream_sched_prio.c	…
stream_sched_rr.c	…
sysctl.c	…
transport.c	…
tsnmap.c	…
ulpevent.c	…
ulpqueue.c	…