All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Dmitry Safonov <dima@arista.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	Mohammad Nassiri <mnassiri@ciena.com>,
	Simon Horman <horms@kernel.org>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] selftests/net: A couple of typos fixes in key-management/rst tests
Date: Thu, 1 Feb 2024 19:13:40 -0800	[thread overview]
Message-ID: <20240201191340.0d952a3f@kernel.org> (raw)
In-Reply-To: <6104436c-4c71-4427-a569-cf98174d0c20@arista.com>

On Fri, 2 Feb 2024 02:30:52 +0000 Dmitry Safonov wrote:
> > Actually, I think there may be an easier fix:
> > 
> > 4. Make sure that client close()s TCP-AO first, making it twsk.
> >    And also make sure that net-ns counters read post server's close().
> > 
> > Will do this, let's see if this fixes the flakiness on the netdev bot :)  
> 
> FWIW, I ended up with this:
> https://lore.kernel.org/all/20240202-unsigned-md5-netns-counters-v1-1-8b90c37c0566@arista.com/
> 
> I reproduced the issue once, running unsigned-md5* in a loop, while in
> another terminal building linux-next with all cores.
> With the patch above, it survived 77 iterations of both ipv4/ipv6 tests
> so far. So, there is a chance it fixes the issue :)

That was quick! Fingers crossed :)

  reply	other threads:[~2024-02-02  3:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30  3:51 [PATCH v2 0/3] selftests/net: A couple of typos fixes in key-management/rst tests Dmitry Safonov
2024-01-30  3:51 ` [PATCH v2 1/3] selftests/net: Argument value mismatch when calling verify_counters() Dmitry Safonov
2024-01-30  3:51 ` [PATCH v2 2/3] selftests/net: Rectify key counters checks Dmitry Safonov
2024-01-30  3:51 ` [PATCH v2 3/3] selftests/net: Repair RST passive reset selftest Dmitry Safonov
2024-02-01  0:36 ` [PATCH v2 0/3] selftests/net: A couple of typos fixes in key-management/rst tests Jakub Kicinski
2024-02-01  0:50   ` Dmitry Safonov
2024-02-01 21:21     ` Jakub Kicinski
2024-02-01 22:25       ` Dmitry Safonov
2024-02-01 23:37         ` Dmitry Safonov
2024-02-02  2:30           ` Dmitry Safonov
2024-02-02  3:13             ` Jakub Kicinski [this message]
2024-02-01  0:40 ` patchwork-bot+netdevbpf

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=20240201191340.0d952a3f@kernel.org \
    --to=kuba@kernel.org \
    --cc=0x7f454c46@gmail.com \
    --cc=davem@davemloft.net \
    --cc=dima@arista.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mnassiri@ciena.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@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 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.