Re: [PATCH] sctp: don't compare hb_timer expire date before starting it

2019-02-22 Thread David Miller
From: kwiecienmac...@gmail.com Date: Fri, 22 Feb 2019 09:45:26 +0100 > From: Maciej Kwiecien > > hb_timer might not start at all for a particular transport because its > start is conditional. In a result a node is not sending heartbeats. > > Function sctp_transport_reset_hb_timer has two roles:

Re: [PATCH] sctp: don't compare hb_timer expire date before starting it

2019-02-22 Thread Marcelo Ricardo Leitner
On Fri, Feb 22, 2019 at 09:45:26AM +0100, kwiecienmac...@gmail.com wrote: > From: Maciej Kwiecien > > hb_timer might not start at all for a particular transport because its > start is conditional. In a result a node is not sending heartbeats. > > Function sctp_transport_reset_hb_timer has two ro

Re: [PATCH] sctp: don't compare hb_timer expire date before starting it

2019-02-22 Thread Sverdlin, Alexander (Nokia - DE/Ulm)
On 22/02/2019 09:45, kwiecienmac...@gmail.com wrote: > From: Maciej Kwiecien > > hb_timer might not start at all for a particular transport because its > start is conditional. In a result a node is not sending heartbeats. > > Function sctp_transport_reset_hb_timer has two roles: > - initial

[PATCH] sctp: don't compare hb_timer expire date before starting it

2019-02-22 Thread kwiecienmaciek
From: Maciej Kwiecien hb_timer might not start at all for a particular transport because its start is conditional. In a result a node is not sending heartbeats. Function sctp_transport_reset_hb_timer has two roles: - initial start of hb_timer for a given transport, - update expire date o