From: David Ahern <dsahern@gmail.com>
To: Stefano Brivio <sbrivio@redhat.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: David Miller <davem@davemloft.net>,
Jianlin Shi <jishi@redhat.com>, Wei Wang <weiwan@google.com>,
Martin KaFai Lau <kafai@fb.com>,
Eric Dumazet <edumazet@google.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH iproute2] iproute: Pass RTM_F_CLONED on dump to fetch cached routes to be flushed
Date: Mon, 24 Jun 2019 15:55:49 -0600 [thread overview]
Message-ID: <209bcb66-2d57-eecf-d1a0-cc86af034e95@gmail.com> (raw)
In-Reply-To: <7ae318a8b632c216df95362524cd4bb5f4f1f537.1560561439.git.sbrivio@redhat.com>
On 6/14/19 7:33 PM, Stefano Brivio wrote:
> diff --git a/ip/iproute.c b/ip/iproute.c
> index 2b3dcc5dbd53..192442b42062 100644
> --- a/ip/iproute.c
> +++ b/ip/iproute.c
> @@ -1602,6 +1602,16 @@ static int save_route_prep(void)
> return 0;
> }
>
> +static int iproute_flush_flags(struct nlmsghdr *nlh, int reqlen)
rename that to iproute_flush_filter to be consistent with
iproute_dump_filter.
Actually, why can't the flush code use iproute_dump_filter?
> +{
> + struct rtmsg *rtm = NLMSG_DATA(nlh);
> +
> + if (filter.cloned)
> + rtm->rtm_flags |= RTM_F_CLONED;
> +
> + return 0;
> +}
> +
> static int iproute_flush(int family, rtnl_filter_t filter_fn)
> {
> time_t start = time(0);
> @@ -1624,7 +1634,7 @@ static int iproute_flush(int family, rtnl_filter_t filter_fn)
> filter.flushe = sizeof(flushb);
>
> for (;;) {
> - if (rtnl_routedump_req(&rth, family, NULL) < 0) {
> + if (rtnl_routedump_req(&rth, family, iproute_flush_flags) < 0) {
> perror("Cannot send dump request");
> return -2;
> }
>
next prev parent reply other threads:[~2019-06-24 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-15 1:33 [PATCH iproute2] iproute: Pass RTM_F_CLONED on dump to fetch cached routes to be flushed Stefano Brivio
2019-06-24 18:20 ` Stefano Brivio
2019-06-24 21:55 ` David Ahern [this message]
2019-06-25 11:40 ` Stefano Brivio
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=209bcb66-2d57-eecf-d1a0-cc86af034e95@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jishi@redhat.com \
--cc=kafai@fb.com \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=netdev@vger.kernel.org \
--cc=sbrivio@redhat.com \
--cc=stephen@networkplumber.org \
--cc=weiwan@google.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).