mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: netdev@vger.kernel.org, virtualization@lists.linux.dev,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 0/3] vsock/test: improve sigpipe test reliability
Date: Sat, 17 May 2025 01:10:35 +0000	[thread overview]
Message-ID: <174744423548.4114923.6817552161649997971.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250514141927.159456-1-sgarzare@redhat.com>

Hello:

This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Wed, 14 May 2025 16:19:24 +0200 you wrote:
> Running the tests continuously I noticed that sometimes the sigpipe
> test would fail due to a race between the control message of the test
> and the vsock transport messages.
> 
> While I was at it I also improved the test by checking the errno we
> expect.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/3] vsock/test: add timeout_usleep() to allow sleeping in timeout sections
    (no matching commit)
  - [net-next,v2,2/3] vsock/test: retry send() to avoid occasional failure in sigpipe test
    https://git.kernel.org/netdev/net-next/c/135a8a4d25a2
  - [net-next,v2,3/3] vsock/test: check also expected errno on sigpipe test
    https://git.kernel.org/netdev/net-next/c/3c6abbe85bcc

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-05-17  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-14 14:19 Stefano Garzarella
2025-05-14 14:19 ` [PATCH net-next v2 1/3] vsock/test: add timeout_usleep() to allow sleeping in timeout sections Stefano Garzarella
2025-05-14 14:19 ` [PATCH net-next v2 2/3] vsock/test: retry send() to avoid occasional failure in sigpipe test Stefano Garzarella
2025-05-14 14:19 ` [PATCH net-next v2 3/3] vsock/test: check also expected errno on " Stefano Garzarella
2025-05-17  1:10 ` patchwork-bot+netdevbpf [this message]

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=174744423548.4114923.6817552161649997971.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    --cc=virtualization@lists.linux.dev \
    /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
all inboxes | Powered by JetHome®