From: patchwork-bot+netdevbpf@kernel.org
To: Fang Jiabao <kaquoin@163.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 v2 1/2] ip route: use the request size as the limit when adding encap
Date: Wed, 11 Nov 2026 00:10:06 +0000 [thread overview]
Message-ID: <179435580642.128546.15113726545917485391.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261109053209.65753-1-kaquoin@163.com>
Hello:
This series was applied to iproute2/iproute2.git (main)
by Stephen Hemminger <stephen@networkplumber.org>:
On Mon, 9 Nov 2026 13:32:08 +0800 you wrote:
> iproute_modify() passes a hardcoded 1024 as the size limit to
> addraw_l() when it adds the encap attribute. The request buffer is
> larger than that, and every other attribute in this function is bounded
> by sizeof(req). With a seg6 encap of 60 segments the request still fits
> in the buffer, but addraw_l() prints "addraw_l ERROR: message exceeded
> bound of 1024" and returns -1. The return value is ignored, so ip sends
> the request without the encap attribute and exits with status 0, and a
> route without encap is installed silently.
>
> [...]
Here is the summary with links:
- [iproute2,v2,1/2] ip route: use the request size as the limit when adding encap
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=c4a39013ba80
- [iproute2,v2,2/2] ip nexthop: use the request size as the limit when adding encap
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1d64d3416d60
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-11-11 0:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 5:32 [PATCH iproute2 v2 1/2] ip route: use the request size as the limit when adding encap Fang Jiabao
2026-11-09 5:32 ` [PATCH iproute2 v2 2/2] ip nexthop: " Fang Jiabao
2026-11-11 0:10 ` 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=179435580642.128546.15113726545917485391.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=kaquoin@163.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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.