From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Gur Stavi <gur.stavi@huawei.com>, Gur Stavi <gur.stavi@huawei.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"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>,
Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v04 2/3] selftests: net/psock_fanout: socket joins fanout when link is down
Date: Mon, 14 Oct 2024 20:39:00 -0400 [thread overview]
Message-ID: <670db9a43fb46_2e1742294ee@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <6f4a506ed5f08f8fc00a966dec8febd1030c6e98.1728802323.git.gur.stavi@huawei.com>
Gur Stavi wrote:
> Modify test_control_group to have toggle parameter.
> When toggle is non-zero, loopback device will be set down for the
> initialization of fd[1] which is still expected to successfully join
> the fanout.
>
> Signed-off-by: Gur Stavi <gur.stavi@huawei.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
next prev parent reply other threads:[~2024-10-15 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 7:15 [PATCH net-next v04 0/3] net: af_packet: allow joining a fanout when link is down Gur Stavi
2024-10-13 7:15 ` [PATCH net-next v04 1/3] af_packet: allow fanout_add when socket is not RUNNING Gur Stavi
2024-10-15 0:38 ` Willem de Bruijn
2024-10-13 7:15 ` [PATCH net-next v04 2/3] selftests: net/psock_fanout: socket joins fanout when link is down Gur Stavi
2024-10-15 0:39 ` Willem de Bruijn [this message]
2024-10-13 7:15 ` [PATCH net-next v04 3/3] selftests: net/psock_fanout: unbound socket fanout Gur Stavi
2024-10-15 0:39 ` Willem de Bruijn
2024-10-15 17:00 ` [PATCH net-next v04 0/3] net: af_packet: allow joining a fanout when link is down 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=670db9a43fb46_2e1742294ee@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gur.stavi@huawei.com \
--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 \
/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).