From: Markus Elfring <Markus.Elfring@web.de>
To: Yohei Kojima <yk@y-koj.net>,
linux-kselftest@vger.kernel.org, netdev@vger.kernel.org
Cc: kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Shuah Khan <shuah@kernel.org>, Simon Horman <horms@kernel.org>
Subject: Re: [PATCH net-next v2 2/2] selftests: net: improve error handling in passive TFO test
Date: Wed, 14 Jan 2026 09:33:12 +0100 [thread overview]
Message-ID: <1696424e-2092-4e47-bd4f-293e2992056b@web.de> (raw)
In-Reply-To: <24707c8133f7095c0e5a94afa69e75c3a80bf6e7.1768312014.git.yk@y-koj.net>
> Improve the error handling in passive TFO test to check the return value
> from sendto(), and to fail if read() or fprintf() failed.
You propose to adjust error detection and corresponding exception handling another bit.
How do you think about to take also another look if further function implementations
would be similarly affected?
Regards,
Markus
next prev parent reply other threads:[~2026-01-14 8:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 14:11 [PATCH net-next v2 0/2] selftests: net: improve error handling in passive TFO test Yohei Kojima
2026-01-13 14:11 ` [PATCH net-next v2 1/2] selftests: net: fix passive TFO test to fail if child processes failed Yohei Kojima
2026-01-13 14:11 ` [PATCH net-next v2 2/2] selftests: net: improve error handling in passive TFO test Yohei Kojima
2026-01-13 14:48 ` Markus Elfring
2026-01-13 15:57 ` Yohei Kojima
2026-01-14 8:33 ` Markus Elfring [this message]
2026-01-15 16:21 ` Yohei Kojima
2026-01-19 14:19 ` [PATCH net-next v2 0/2] " 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=1696424e-2092-4e47-bd4f-293e2992056b@web.de \
--to=markus.elfring@web.de \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=yk@y-koj.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