DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/other Bug 1731] FIB insertion error(-28) after remove all rules
Date: Thu, 26 Jun 2025 09:36:58 +0000	[thread overview]
Message-ID: <bug-1731-3@https.bugs.dpdk.org/> (raw)

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

https://bugs.dpdk.org/show_bug.cgi?id=1731

            Bug ID: 1731
           Summary: FIB insertion error(-28) after remove all rules
           Product: DPDK
           Version: 25.03
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: other
          Assignee: dev@dpdk.org
          Reporter: kipi@servers.com
  Target Milestone: ---

Created attachment 321
  --> https://bugs.dpdk.org/attachment.cgi?id=321&action=edit
FIB error example

The error is due to overflow of the internal FIB counter "rsvd_tbl8s". After
this error occurs, it is impossible to add any rules even the FIB is empty.

To reproduce this error, simply insert two IP addresses of the following type
with the same next-hope parameter (this is important):
struct Network {
    uint32_t ip;
    uint16_t prefix;
};

/*
    first insertion with prefix less than 25 doesn't allocate tbl8 entry
    second insertion with prefix more than 24 will allocate tbl8 entry BUT only
when we pass the different next hope
*/
const struct Network state[] = {
    {0x3000000, 15}, {0x3000520, 29}
};

and delete them. Deleting the first rule will allocate tbl8 entry but
"rsvd_tbl8s" counter won't increment. Deleting the second rule will decrease
the counter "rsvd_tbl8s" and it will overflow.

The full reproduce program is in attachment.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #2: Type: text/html, Size: 3557 bytes --]

                 reply	other threads:[~2025-06-26  9:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1731-3@https.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@dpdk.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 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).