netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Vadim Kochan <vadim4j@gmail.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] ip monitor: Dont print timestamp or banner-label for cloned routes
Date: Thu, 04 Sep 2014 23:29:35 +0400	[thread overview]
Message-ID: <5408BD9F.9060107@cogentembedded.com> (raw)
In-Reply-To: <1409856738-1938-1-git-send-email-vadim4j@gmail.com>

Hello.

On 09/04/2014 10:52 PM, Vadim Kochan wrote:

> This is ugly fix but solves the case when timestamp
> or banner-label is printed before the cloned route will be skipped
> by iproute filter which filters out all cached routes by default.
> In such case timestamp will be printed twice:

>      Timestamp: Thu Sep  4 19:46:59 2014 457933 usec
>      Timestamp: Thu Sep  4 19:47:07 2014 977970 usec
>      10.3.5.1 dev wlp3s0 lladdr XX:XX:XX:XX:XX:XX STALE

> Signed-off-by: Vadim Kochan <vadim4j@gmail.com>
> ---
>   ip/ipmonitor.c | 13 ++++++++++---
>   1 file changed, 10 insertions(+), 3 deletions(-)

> diff --git a/ip/ipmonitor.c b/ip/ipmonitor.c
> index 70f2a7a..2bd3fed 100644
> --- a/ip/ipmonitor.c
> +++ b/ip/ipmonitor.c
[...]
> @@ -53,6 +50,12 @@ static int accept_msg(const struct sockaddr_nl *who,
>   			return -1;
>   		}
>
> +		if (r->rtm_flags&RTM_F_CLONED)

    Judging on the patched code, spaces are needed around &.

> +			return 0;
> +
> +		if (timestamp)
> +			print_timestamp(fp);
> +
>   		if (r->rtm_family == RTNL_FAMILY_IPMR ||
>   		    r->rtm_family == RTNL_FAMILY_IP6MR) {
>   			if (prefix_banner)
[...]

WBR, Sergei

  reply	other threads:[~2014-09-04 19:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 18:52 [PATCH] ip monitor: Dont print timestamp or banner-label for cloned routes Vadim Kochan
2014-09-04 19:29 ` Sergei Shtylyov [this message]
2014-09-04 19:35   ` Vadim Kochan
2014-09-04 19:54     ` Vlad Yasevich
2014-09-04 19:59       ` Vadim Kochan
2014-09-04 20:01         ` Vadim Kochan
2014-09-04 21:19           ` Sergei Shtylyov

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=5408BD9F.9060107@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=netdev@vger.kernel.org \
    --cc=vadim4j@gmail.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).