All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Weiming Shi <bestswngs@gmail.com>
Cc: linux-sctp@vger.kernel.org, marcelo.leitner@gmail.com,
	lucien.xin@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	xmei5@asu.edu, stable@vger.kernel.org
Subject: Re: [PATCH net] sctp: validate STALE_COOKIE cause length before reading staleness
Date: Fri, 10 Jul 2026 15:00:06 +0000	[thread overview]
Message-ID: <178369560614.725168.2626506030480279304.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260704033545.2438373-2-bestswngs@gmail.com>

Hello:

This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:

On Fri,  3 Jul 2026 20:35:46 -0700 you wrote:
> When an ERROR chunk with a STALE_COOKIE cause is received in the
> COOKIE_ECHOED state, sctp_sf_do_5_2_6_stale() reads the 4-byte Measure
> of Staleness that follows the cause header:
> 
> 	err   = (struct sctp_errhdr *)(chunk->skb->data);
> 	stale = ntohl(*(__be32 *)((u8 *)err + sizeof(*err)));
> 
> [...]

Here is the summary with links:
  - [net] sctp: validate STALE_COOKIE cause length before reading staleness
    https://git.kernel.org/netdev/net/c/1cd23ca80784

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



      parent reply	other threads:[~2026-07-10 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-04  3:35 [PATCH net] sctp: validate STALE_COOKIE cause length before reading staleness Weiming Shi
2026-07-05 19:12 ` Xin Long
2026-07-10 15:00 ` 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=178369560614.725168.2626506030480279304.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bestswngs@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.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 \
    --cc=stable@vger.kernel.org \
    --cc=xmei5@asu.edu \
    /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.