Re: [PATCH net] sctp: not allow transport timeout value less than HZ/5 for hb_timer

2018-06-05 Thread David Miller
From: Xin Long Date: Tue, 5 Jun 2018 12:16:58 +0800 > syzbot reported a rcu_sched self-detected stall on CPU which is caused > by too small value set on rto_min with SCTP_RTOINFO sockopt. With this > value, hb_timer will get stuck there, as in its timer handler it starts > this timer again with

Re: [PATCH net] sctp: not allow transport timeout value less than HZ/5 for hb_timer

2018-06-05 Thread Neil Horman
On Tue, Jun 05, 2018 at 12:16:58PM +0800, Xin Long wrote: > syzbot reported a rcu_sched self-detected stall on CPU which is caused > by too small value set on rto_min with SCTP_RTOINFO sockopt. With this > value, hb_timer will get stuck there, as in its timer handler it starts > this timer again wi

[PATCH net] sctp: not allow transport timeout value less than HZ/5 for hb_timer

2018-06-04 Thread Xin Long
syzbot reported a rcu_sched self-detected stall on CPU which is caused by too small value set on rto_min with SCTP_RTOINFO sockopt. With this value, hb_timer will get stuck there, as in its timer handler it starts this timer again with this value, then goes to the timer handler again. This problem