From: Ido Schimmel <idosch@nvidia.com>
To: Eric Dumazet <edumazet@google.com>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next 2/2] rtnetlink: use xarray iterator to implement rtnl_dump_ifinfo()
Date: Mon, 12 Feb 2024 18:10:16 +0200 [thread overview]
Message-ID: <ZcpC6Gk9fmJrv80V@shredder> (raw)
In-Reply-To: <20240211214404.1882191-3-edumazet@google.com>
On Sun, Feb 11, 2024 at 09:44:04PM +0000, Eric Dumazet wrote:
> Adopt net->dev_by_index as I did in commit 0e0939c0adf9
> ("net-procfs: use xarray iterator to implement /proc/net/dev")
>
> This makes sure an existing device is always visible in the dump,
> regardless of concurrent insertions/deletions.
>
> v2: added suggestions from Jakub Kicinski and Ido Schimmel,
> thanks for the help !
>
> Link: https://lore.kernel.org/all/20240209142441.6c56435b@kernel.org/
> Link: https://lore.kernel.org/all/ZckR-XOsULLI9EHc@shredder/
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2024-02-12 16:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-11 21:44 [PATCH v2 net-next 0/2] net: use net->dev_by_index in two places Eric Dumazet
2024-02-11 21:44 ` [PATCH v2 net-next 1/2] vlan: use xarray iterator to implement /proc/net/vlan/config Eric Dumazet
2024-02-12 16:09 ` Ido Schimmel
2024-02-11 21:44 ` [PATCH v2 net-next 2/2] rtnetlink: use xarray iterator to implement rtnl_dump_ifinfo() Eric Dumazet
2024-02-12 16:10 ` Ido Schimmel [this message]
2024-02-14 2:50 ` [PATCH v2 net-next 0/2] net: use net->dev_by_index in two places patchwork-bot+netdevbpf
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=ZcpC6Gk9fmJrv80V@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 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.