public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch•org>
To: David Ahern <dsahern@gmail•com>
Cc: Petr Machata <petrm@nvidia•com>, Ido Schimmel <idosch@nvidia•com>,
	netdev@vger•kernel.org, stephen@networkplumber•org,
	razor@blackwall•org
Subject: Re: [PATCH iproute2-next] bridge: Add backup nexthop ID support
Date: Wed, 2 Aug 2023 20:22:29 +0300	[thread overview]
Message-ID: <ZMqQ1W+TxoPOAodC@shredder> (raw)
In-Reply-To: <16c562ce-433d-ac78-95ad-101bef710efc@gmail.com>

On Wed, Aug 02, 2023 at 09:35:12AM -0600, David Ahern wrote:
> ugh, please send a fix.

Will send a fix tomorrow. Seems to be fixed by [1], but we might need
something similar for the bucket dump.

[1]
diff --git a/net/ipv4/nexthop.c b/net/ipv4/nexthop.c
index 93f14d39fef6..1bd92acbc6c5 100644
--- a/net/ipv4/nexthop.c
+++ b/net/ipv4/nexthop.c
@@ -3170,7 +3170,7 @@ static int nh_valid_dump_req(const struct nlmsghdr *nlh,
 }
 
 struct rtm_dump_nh_ctx {
-       u32 idx;
+       u64 idx;
 };
 
 static struct rtm_dump_nh_ctx *
@@ -3192,7 +3192,7 @@ static int rtm_dump_walk_nexthops(struct sk_buff *skb,
                                  void *data)
 {
        struct rb_node *node;
-       int s_idx;
+       u64 s_idx;
        int err;
 
        s_idx = ctx->idx;

      reply	other threads:[~2023-08-02 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-01 15:21 [PATCH iproute2-next] bridge: Add backup nexthop ID support Ido Schimmel
2023-08-02  9:55 ` Petr Machata
2023-08-02 12:34   ` Ido Schimmel
2023-08-02 13:35     ` Petr Machata
2023-08-02 15:35     ` David Ahern
2023-08-02 17:22       ` Ido Schimmel [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=ZMqQ1W+TxoPOAodC@shredder \
    --to=idosch@idosch$(echo .)org \
    --cc=dsahern@gmail$(echo .)com \
    --cc=idosch@nvidia$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=petrm@nvidia$(echo .)com \
    --cc=razor@blackwall$(echo .)org \
    --cc=stephen@networkplumber$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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