From: David Miller <davem@davemloft.net>
To: hadi@cyberus.ca
Cc: nakam@linux-ipv6.org, kaber@trash.net,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [RFC PATCH net-next-2.6]: xfrm: Introduce LINUX_MIB_XFRMFWDHDRERROR
Date: Wed, 17 Feb 2010 13:49:46 -0800 (PST) [thread overview]
Message-ID: <20100217.134946.106752388.davem@davemloft.net> (raw)
In-Reply-To: <1266406852.3799.7.camel@bigi>
From: jamal <hadi@cyberus.ca>
Date: Wed, 17 Feb 2010 06:40:52 -0500
> xfrm: Introduce LINUX_MIB_XFRMFWDHDRERROR
>
> XFRMINHDRERROR counter is ambigous when validating forwarding
> path. It makes it tricky to debug when you have both in and fwd
> validation.
>
> Signed-off-by: Jamal Hadi Salim <hadi@cyberus.ca>
This should be fine, the tools just parse the lines individually
as "string integer" pairs.
If you want to be super anal, add the new counter to the end of
the array.
next prev parent reply other threads:[~2010-02-17 21:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 11:40 [RFC PATCH net-next-2.6]: xfrm: Introduce LINUX_MIB_XFRMFWDHDRERROR jamal
2010-02-17 21:49 ` David Miller [this message]
2010-02-18 13:35 ` jamal
2010-02-18 23:44 ` David Miller
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=20100217.134946.106752388.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=herbert@gondor.apana.org.au \
--cc=kaber@trash.net \
--cc=nakam@linux-ipv6.org \
--cc=netdev@vger.kernel.org \
/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).