From: Steffen Klassert <steffen.klassert@secunet.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: <netdev@vger.kernel.org>, <cagney@libreswan.org>
Subject: Re: [PATCH ipsec 2/2] espintcp: count packets dropped in espintcp_rcv
Date: Fri, 31 Jul 2020 09:02:43 +0200 [thread overview]
Message-ID: <20200731070243.GF20687@gauss3.secunet.de> (raw)
In-Reply-To: <fc6daad7e7cc0ec9cc75dd3489dada90f8d19275.1596038944.git.sd@queasysnail.net>
On Wed, Jul 29, 2020 at 06:38:43PM +0200, Sabrina Dubroca wrote:
> Currently, espintcp_rcv drops packets silently, which makes debugging
> issues difficult. Count packets as either XfrmInHdrError (when the
> packet was too short or contained invalid data) or XfrmInError (for
> other issues).
>
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Also applied, thanks Sabrina!
next prev parent reply other threads:[~2020-07-31 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 16:38 [PATCH ipsec 1/2] espintcp: handle short messages instead of breaking the encap socket Sabrina Dubroca
2020-07-29 16:38 ` [PATCH ipsec 2/2] espintcp: count packets dropped in espintcp_rcv Sabrina Dubroca
2020-07-31 7:02 ` Steffen Klassert [this message]
2020-07-31 7:02 ` [PATCH ipsec 1/2] espintcp: handle short messages instead of breaking the encap socket Steffen Klassert
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=20200731070243.GF20687@gauss3.secunet.de \
--to=steffen.klassert@secunet.com \
--cc=cagney@libreswan.org \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).