[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220421.111807.1804226251338066304.davem@davemloft.net>
Date: Thu, 21 Apr 2022 11:18:07 +0100 (BST)
From: David Miller <davem@...emloft.net>
To: lucien.xin@...il.com
Cc: netdev@...r.kernel.org, linux-sctp@...r.kernel.org,
kuba@...nel.org, marcelo.leitner@...il.com, nhorman@...driver.com
Subject: Re: [PATCH net] sctp: check asoc strreset_chunk in
sctp_generate_reconf_event
From: Xin Long <lucien.xin@...il.com>
Date: Wed, 20 Apr 2022 16:52:41 -0400
> diff --git a/net/sctp/sm_sideeffect.c b/net/sctp/sm_sideeffect.c
> index b3815b568e8e..463c4a58d2c3 100644
> --- a/net/sctp/sm_sideeffect.c
> +++ b/net/sctp/sm_sideeffect.c
> @@ -458,6 +458,10 @@ void sctp_generate_reconf_event(struct timer_list *t)
> goto out_unlock;
> }
>
> + /* This happens when the response arrives after the timer is triggered. */
> + if (!asoc->strreset_chunk)
> + goto out_unlock;
> +
This will return 0 because that is error's value right there, intentional?
Thanks.
Powered by blists - more mailing lists