From: patchwork-bot+netdevbpf@kernel•org
To: Alexander Mikhalitsyn <alexander.mikhalitsyn@virtuozzo•com>
Cc: netdev@vger•kernel.org, dsahern@gmail•com,
stephen@networkplumber•org, avagin@gmail•com,
alexander@mihalicyn•com
Subject: Re: [PATCHv5 iproute2] ip route: ignore ENOENT during save if RT_TABLE_MAIN is being dumped
Date: Wed, 07 Jul 2021 14:50:03 +0000 [thread overview]
Message-ID: <162566940335.13544.6152983012879947638.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210707122201.14618-1-alexander.mikhalitsyn@virtuozzo.com>
Hello:
This patch was applied to iproute2/iproute2.git (refs/heads/main):
On Wed, 7 Jul 2021 15:22:01 +0300 you wrote:
> We started to use in-kernel filtering feature which allows to get only
> needed tables (see iproute_dump_filter()). From the kernel side it's
> implemented in net/ipv4/fib_frontend.c (inet_dump_fib), net/ipv6/ip6_fib.c
> (inet6_dump_fib). The problem here is that behaviour of "ip route save"
> was changed after
> c7e6371bc ("ip route: Add protocol, table id and device to dump request").
> If filters are used, then kernel returns ENOENT error if requested table
> is absent, but in newly created net namespace even RT_TABLE_MAIN table
> doesn't exist. It is really allocated, for instance, after issuing
> "ip l set lo up".
>
> [...]
Here is the summary with links:
- [PATCHv5,iproute2] ip route: ignore ENOENT during save if RT_TABLE_MAIN is being dumped
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=459ce6e3d792
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-07-07 14:51 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 15:03 [PATCH iproute2] ip route: ignore ENOENT during save if RT_TABLE_MAIN is being dumped Alexander Mikhalitsyn
2021-06-23 15:36 ` David Ahern
2021-06-23 16:11 ` Alexander Mikhalitsyn
2021-06-24 15:28 ` [PATCHv2 " Alexander Mikhalitsyn
2021-06-24 15:36 ` Stephen Hemminger
2021-06-24 15:40 ` Alexander Mikhalitsyn
2021-06-25 10:59 ` Alexander Mikhalitsyn
2021-06-25 10:44 ` [PATCHv3 " Alexander Mikhalitsyn
2021-06-27 21:54 ` Stephen Hemminger
2021-06-28 6:31 ` Alexander Mikhalitsyn
2021-06-28 17:17 ` Stephen Hemminger
2021-06-28 17:21 ` Alexander Mikhalitsyn
2021-06-29 15:51 ` [PATCHv4 " Alexander Mikhalitsyn
2021-07-06 7:47 ` Alexander Mikhalitsyn
2021-07-06 15:34 ` Stephen Hemminger
2021-07-06 15:44 ` Alexander Mikhalitsyn
2021-07-06 16:18 ` Stephen Hemminger
2021-07-06 17:17 ` Alexander Mikhalitsyn
2021-07-07 0:05 ` Stephen Hemminger
2021-07-07 12:22 ` Alexander Mikhalitsyn
2021-07-07 14:31 ` Stephen Hemminger
2021-07-07 14:32 ` Alexander Mikhalitsyn
2021-07-07 12:09 ` [PATCHv5 " Alexander Mikhalitsyn
2021-07-07 12:22 ` Alexander Mikhalitsyn
2021-07-07 14:35 ` Stephen Hemminger
2021-07-07 14:38 ` Alexander Mikhalitsyn
2021-07-07 14:50 ` patchwork-bot+netdevbpf [this message]
2021-07-11 10:59 ` Roi Dayan
2021-07-11 11:09 ` Roi Dayan
2021-07-11 11:12 ` Alexander Mihalicyn
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=162566940335.13544.6152983012879947638.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=alexander.mikhalitsyn@virtuozzo$(echo .)com \
--cc=alexander@mihalicyn$(echo .)com \
--cc=avagin@gmail$(echo .)com \
--cc=dsahern@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.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