From: Antony Antony <antony@phenome.org>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: Antony Antony <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>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>
Subject: Re: [devel-ipsec] [PATCH ipsec-next v11 2/4] xfrm: Add dir validation to "out" data path lookup
Date: Tue, 23 Apr 2024 14:36:25 +0200 [thread overview]
Message-ID: <ZierSZe5fykqwnFz@Antony2201.local> (raw)
In-Reply-To: <ZiYz5Om5OtivN7cV@hog>
On Mon, Apr 22, 2024 at 11:54:44AM +0200, Sabrina Dubroca via Devel wrote:
> 2024-04-22, 00:27:48 +0200, Antony Antony wrote:
> > diff --git a/net/xfrm/xfrm_proc.c b/net/xfrm/xfrm_proc.c
> > index 5f9bf8e5c933..98606f1078f7 100644
> > --- a/net/xfrm/xfrm_proc.c
> > +++ b/net/xfrm/xfrm_proc.c
> > @@ -41,6 +41,7 @@ static const struct snmp_mib xfrm_mib_list[] = {
> > SNMP_MIB_ITEM("XfrmFwdHdrError", LINUX_MIB_XFRMFWDHDRERROR),
> > SNMP_MIB_ITEM("XfrmOutStateInvalid", LINUX_MIB_XFRMOUTSTATEINVALID),
> > SNMP_MIB_ITEM("XfrmAcquireError", LINUX_MIB_XFRMACQUIREERROR),
> > + SNMP_MIB_ITEM("XfrmOutStateDirError", LINUX_MIB_XFRMOUTSTATEDIRERROR),
>
> This needs a corresponding entry in Documentation/networking/xfrm_proc.rst
fixed. I added both in and out error to it; v12.
-antony
next prev parent reply other threads:[~2024-04-23 12:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 22:23 [PATCH ipsec-next v11 0/4] xfrm: Introduce direction attribute for SA Antony Antony
2024-04-21 22:26 ` [PATCH ipsec-next v11 1/4] xfrm: Add Direction to the SA in or out Antony Antony
2024-04-21 22:27 ` [PATCH ipsec-next v11 2/4] xfrm: Add dir validation to "out" data path lookup Antony Antony
2024-04-22 9:54 ` Sabrina Dubroca
2024-04-23 12:36 ` Antony Antony [this message]
2024-04-21 22:29 ` [PATCH ipsec-next v11 3/4] xfrm: Add dir validation to "in" " Antony Antony
2024-04-21 22:30 ` [PATCH ipsec-next v11 4/4] xfrm: Restrict SA direction attribute to specific netlink message types Antony Antony
2024-04-22 13:05 ` [PATCH ipsec-next v11 0/4] xfrm: Introduce direction attribute for SA Jakub Kicinski
2024-04-23 12:34 ` 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=ZierSZe5fykqwnFz@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 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).