From: David Ahern <dsahern@gmail.com>
To: Stanislav Fomichev <stfomichev@gmail.com>, netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2-next] ip: support setting multiple features
Date: Sat, 31 May 2025 10:11:58 -0600 [thread overview]
Message-ID: <d136f120-aaf2-4b2e-8e11-b62462e79e34@gmail.com> (raw)
In-Reply-To: <e55dec9ff62227636a4782bda3cfa7e063e614f0.1748382868.git.stfomichev@gmail.com>
On 5/27/25 3:55 PM, Stanislav Fomichev wrote:
> Commit a043bea75002 ("ip route: add support for TCP usec TS") added
> support for tcp_usec_ts but the existing code was not adjusted
> to handle multiple features in the same invocation:
>
> $ ip route add .. dev .. features tcp_usec_ts ecn
> Error: either "to" is duplicate, or "ecn" is garbage.
>
> The code exits the while loop as soon as it encounters any feature,
> make it more flexible. Tested with the following:
>
> $ ip route add .. dev .. features tcp_usec_ts ecn
> $ ip route add .. dev .. features tcp_usec_ts ecn quickack 1
>
> Cc: Stephen Hemminger <stephen@networkplumber.org>
> Fixes: a043bea75002 ("ip route: add support for TCP usec TS")
> Signed-off-by: Stanislav Fomichev <stfomichev@gmail.com>
> ---
> v2: separate logic into separate function (Stephen)
> ---
> ip/iproute.c | 38 ++++++++++++++++++++++++++++----------
> 1 file changed, 28 insertions(+), 10 deletions(-)
>
applied to iproute2-next. Thanks
prev parent reply other threads:[~2025-05-31 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 21:55 [PATCH iproute2-next] ip: support setting multiple features Stanislav Fomichev
2025-05-31 16:11 ` David Ahern [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=d136f120-aaf2-4b2e-8e11-b62462e79e34@gmail.com \
--to=dsahern@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=stfomichev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).