From: Thomas Monjalon <thomas@monjalon.net>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] fib6: fix adding default route as first route
Date: Tue, 17 Oct 2023 15:27:31 +0200 [thread overview]
Message-ID: <1832985.QCnGb9OGeP@thomas> (raw)
In-Reply-To: <20231002151201.675868-1-vladimir.medvedkin@intel.com>
02/10/2023 17:12, Vladimir Medvedkin:
> Currently when adding default route as first route
> it is not added and no error is reported.
> When we enter the loop over an address range in
> the general case we will eventually reach the check
> for when the range has ended, and exit the loop.
> However when adding default route as first route,
> since address range covered begins and ends at zero
> this also triggers loop exit without writing to the table.
>
> Fixed by adding check for default route,
> i.e. both ledge and redge are equal to 0::0.
>
> Bugzilla ID: 1272
> Fixes: c3e12e0f0354 ("fib: add dataplane algorithm for IPv6")
> Cc: stable@dpdk.org
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Applied, thanks.
prev parent reply other threads:[~2023-10-17 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 15:12 Vladimir Medvedkin
2023-10-17 13:27 ` Thomas Monjalon [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=1832985.QCnGb9OGeP@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=vladimir.medvedkin@intel.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).