All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antony Antony <antony@phenome.org>
To: nicolas.dichtel@6wind.com
Cc: antony.antony@secunet.com,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	devel@linux-ipsec.org, Leon Romanovsky <leon@kernel.org>,
	Eyal Birger <eyal.birger@gmail.com>,
	Sabrina Dubroca <sd@queasysnail.net>
Subject: Re: [PATCH ipsec-next v10 3/3] xfrm: Add dir validation to "in" data path lookup
Date: Mon, 15 Apr 2024 21:54:37 +0200	[thread overview]
Message-ID: <Zh2F_U5E9f3TSK35@Antony2201.local> (raw)
In-Reply-To: <424a52f9-df2f-4205-ab9d-cd943b8a7398@6wind.com>

On Fri, Apr 12, 2024 at 03:54:51PM +0200, Nicolas Dichtel via Devel wrote:
> Le 11/04/2024 à 11:42, Antony Antony a écrit :
> > grep -vw 0 /proc/net/xfrm_stat
> > XfrmInDirError          	3
> > 
> > Signed-off-by: Antony Antony <antony.antony@secunet.com>
> > ---
> >  include/uapi/linux/snmp.h |  1 +
> >  net/ipv6/xfrm6_input.c    |  7 +++++++
> >  net/xfrm/xfrm_input.c     | 11 +++++++++++
> >  net/xfrm/xfrm_proc.c      |  1 +
> >  4 files changed, 20 insertions(+)
> > 
> > diff --git a/include/uapi/linux/snmp.h b/include/uapi/linux/snmp.h
> > index 00e179c382c0..da5714e9a311 100644
> > --- a/include/uapi/linux/snmp.h
> > +++ b/include/uapi/linux/snmp.h
> > @@ -338,6 +338,7 @@ enum
> >  	LINUX_MIB_XFRMOUTSTATEINVALID,		/* XfrmOutStateInvalid */
> >  	LINUX_MIB_XFRMACQUIREERROR,		/* XfrmAcquireError */
> >  	LINUX_MIB_XFRMOUTDIRERROR,		/* XfrmOutDirError */
> > +	LINUX_MIB_XFRMINDIRERROR,		/* XfrmInDirError */
> Same here:
> LINUX_MIB_XFRMINSTATEDIRERROR / XfrmInStateDirError

yes thanks.

  reply	other threads:[~2024-04-15 19:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-11  9:40 [PATCH ipsec-next v10 1/3] xfrm: Add Direction to the SA in or out Antony Antony
2024-04-11  9:42 ` [PATCH ipsec-next v10 2/3] xfrm: Add dir validation to "out" data path lookup Antony Antony
2024-04-12 13:49   ` Nicolas Dichtel
2024-04-12 13:53   ` Nicolas Dichtel
2024-04-18  9:24   ` Simon Horman
2024-04-21 22:13     ` Antony Antony
2024-04-11  9:42 ` [PATCH ipsec-next v10 3/3] xfrm: Add dir validation to "in" " Antony Antony
2024-04-12 13:54   ` Nicolas Dichtel
2024-04-15 19:54     ` Antony Antony [this message]
2024-04-11 11:41 ` [PATCH ipsec-next v10 1/3] xfrm: Add Direction to the SA in or out Leon Romanovsky
2024-04-11 16:20   ` [devel-ipsec] " Paul Wouters
2024-04-11 16:40     ` Christian Hopps
2024-04-11 17:05     ` Leon Romanovsky
2024-04-15 12:21 ` Sabrina Dubroca
2024-04-16  7:10   ` [devel-ipsec] " Antony Antony
2024-04-16  8:36     ` Sabrina Dubroca
2024-04-21 22:04       ` Antony Antony
2024-04-22  9:16         ` Sabrina Dubroca
2024-04-22  9:54           ` Nicolas Dichtel
2024-04-23 12:42           ` Antony Antony

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=Zh2F_U5E9f3TSK35@Antony2201.local \
    --to=antony@phenome.org \
    --cc=antony.antony@secunet.com \
    --cc=davem@davemloft.net \
    --cc=devel@linux-ipsec.org \
    --cc=edumazet@google.com \
    --cc=eyal.birger@gmail.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.dichtel@6wind.com \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=steffen.klassert@secunet.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.