From: patchwork-bot+netdevbpf@kernel.org
To: Jun Yang <juny24602@gmail.com>
Cc: linux-sctp@vger.kernel.org, netdev@vger.kernel.org,
marcelo.leitner@gmail.com, lucien.xin@gmail.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, junvyyang@tencent.com
Subject: Re: [PATCH net v4 0/2] sctp: handle wrapped and duplicate RECONF responses
Date: Tue, 25 Aug 2026 12:30:08 +0000 [thread overview]
Message-ID: <178766100864.3428215.18068978210796260872.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260824081832.98717-1-juny24602@gmail.com>
Hello:
This series was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 24 Aug 2026 16:18:18 +0800 you wrote:
> From: Jun Yang <junvyyang@tencent.com>
>
> Fix response sequence zero lookup first, then make RECONF response
> handling idempotent with an outstanding-request bitmask.
>
> Jun Yang (2):
> sctp: distinguish sequence zero from wildcard in reconf lookup
> sctp: fix stream->outcnt underflow on duplicate RECONF responses
>
> [...]
Here is the summary with links:
- [net,v4,1/2] sctp: distinguish sequence zero from wildcard in reconf lookup
https://git.kernel.org/netdev/net/c/63f44178f0a0
- [net,v4,2/2] sctp: fix stream->outcnt underflow on duplicate RECONF responses
https://git.kernel.org/netdev/net/c/3faf13aff243
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-25 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 8:18 [PATCH net v4 0/2] sctp: handle wrapped and duplicate RECONF responses Jun Yang
2026-08-24 8:18 ` [PATCH net v4 1/2] sctp: distinguish sequence zero from wildcard in reconf lookup Jun Yang
2026-08-24 8:18 ` [PATCH net v4 2/2] sctp: fix stream->outcnt underflow on duplicate RECONF responses Jun Yang
2026-08-25 12:30 ` 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=178766100864.3428215.18068978210796260872.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=junvyyang@tencent.com \
--cc=juny24602@gmail.com \
--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 \
--cc=pabeni@redhat.com \
/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.