All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, linux-sctp@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org, marcelo.leitner@gmail.com
Subject: Re: [PATCH net] sctp: fix a SCTP_MIB_CURRESTAB leak in sctp_sf_do_dupcook_b
Date: Mon, 03 May 2021 20:40:10 +0000	[thread overview]
Message-ID: <162007441030.32677.12037671567310177974.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <98b2f435ec48fba6c9bbb63908c887f15f67a98d.1619988080.git.lucien.xin@gmail.com>

Hello:

This patch was applied to netdev/net.git (refs/heads/master):

On Mon,  3 May 2021 04:41:20 +0800 you wrote:
> Normally SCTP_MIB_CURRESTAB is always incremented once asoc enter into
> ESTABLISHED from the state < ESTABLISHED and decremented when the asoc
> is being deleted.
> 
> However, in sctp_sf_do_dupcook_b(), the asoc's state can be changed to
> ESTABLISHED from the state >= ESTABLISHED where it shouldn't increment
> SCTP_MIB_CURRESTAB. Otherwise, one asoc may increment MIB_CURRESTAB
> multiple times but only decrement once at the end.
> 
> [...]

Here is the summary with links:
  - [net] sctp: fix a SCTP_MIB_CURRESTAB leak in sctp_sf_do_dupcook_b
    https://git.kernel.org/netdev/net/c/f282df039126

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2021-05-03 20:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 20:41 [PATCH net] sctp: fix a SCTP_MIB_CURRESTAB leak in sctp_sf_do_dupcook_b Xin Long
2021-05-03 20:40 ` patchwork-bot+netdevbpf [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=162007441030.32677.12037671567310177974.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.