From: Guillaume Nault <gnault@redhat.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Shuah Khan <shuah@kernel.org>,
David Ahern <dsahern@kernel.org>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Florian Westphal <fw@strlen.de>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 3/3] selftests: net: don't access /dev/stdout in pmtu.sh
Date: Tue, 30 Jan 2024 20:40:45 +0100 [thread overview]
Message-ID: <ZblQvSCgTSs6FfQU@debian> (raw)
In-Reply-To: <23d7592c5d77d75cff9b34f15c227f92e911c2ae.1706635101.git.pabeni@redhat.com>
On Tue, Jan 30, 2024 at 06:47:18PM +0100, Paolo Abeni wrote:
> When running the pmtu.sh via the kselftest infra, accessing
> /dev/stdout gives unexpected results:
> # dd: failed to open '/dev/stdout': Device or resource busy
> # TEST: IPv4, bridged vxlan4: PMTU exceptions [FAIL]
>
> Let dd use directly the standard output to fix the above:
> # TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects [ OK ]
>
Reviewed-by: Guillaume Nault <gnault@redhat.com>
next prev parent reply other threads:[~2024-01-30 19:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 17:47 [PATCH net 0/3] selftests: net: a few pmtu.sh fixes Paolo Abeni
2024-01-30 17:47 ` [PATCH net 1/3] selftests: net: add missing config for pmtu.sh tests Paolo Abeni
2024-01-30 19:30 ` Guillaume Nault
2024-01-30 17:47 ` [PATCH net 2/3] selftests: net: fix available tunnels detection Paolo Abeni
2024-01-30 19:38 ` Guillaume Nault
2024-01-30 17:47 ` [PATCH net 3/3] selftests: net: don't access /dev/stdout in pmtu.sh Paolo Abeni
2024-01-30 19:40 ` Guillaume Nault [this message]
2024-01-30 19:13 ` [PATCH net 0/3] selftests: net: a few pmtu.sh fixes David Ahern
2024-02-01 5:20 ` 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=ZblQvSCgTSs6FfQU@debian \
--to=gnault@redhat.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@kernel.org \
--cc=vadim.fedorenko@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;
as well as URLs for NNTP newsgroup(s).