From: Gur Stavi <gur.stavi@huawei.com>
To: 'Willem de Bruijn' <willemdebruijn.kernel@gmail.com>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
<netdev@vger.kernel.org>, <pabeni@redhat.com>, <shuah@kernel.org>
Subject: RE: [PATCH net-next v02 1/2] af_packet: allow fanout_add when socket is not RUNNING
Date: Thu, 10 Oct 2024 14:49:19 +0300 [thread overview]
Message-ID: <003001db1b0a$77bcdad0$67369070$@huawei.com> (raw)
In-Reply-To:
> I realized another possible problem. We should consider adding ifindex
> Field to struct packet_fanout to be used for lookup of an existing match.
> There is little sense to bind sockets to different interfaces and then
> put them in the same fanout group.
> If you agree, I can prepare a separate patch for that.
My mistake: testing match->prot_hook.dev takes care of that.
next prev parent reply other threads:[~2024-10-10 11:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 10:27 [PATCH net-next v02 0/2] net: af_packet: allow joining a fanout when link is down Gur Stavi
2024-10-08 10:27 ` [PATCH net-next v02 1/2] af_packet: allow fanout_add when socket is not RUNNING Gur Stavi
2024-10-08 14:26 ` Willem de Bruijn
2024-10-09 6:58 ` Gur Stavi
2024-10-09 13:51 ` Willem de Bruijn
2024-10-09 18:03 ` Gur Stavi
2024-10-10 0:30 ` Willem de Bruijn
2024-10-10 7:08 ` Gur Stavi
2024-10-10 14:21 ` Willem de Bruijn
2024-10-10 16:14 ` Gur Stavi
2024-10-10 22:12 ` Willem de Bruijn
2024-10-11 5:17 ` Gur Stavi
2024-10-11 14:24 ` Willem de Bruijn
2024-10-11 9:02 ` Gur Stavi
2024-10-11 14:35 ` Willem de Bruijn
2024-10-11 17:12 ` Gur Stavi
2024-10-11 19:08 ` Willem de Bruijn
2024-10-10 11:49 ` Gur Stavi [this message]
2024-10-08 10:27 ` [PATCH net-next v02 2/2] selftests: net/psock_fanout: socket joins fanout when link is down Gur Stavi
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='003001db1b0a$77bcdad0$67369070$@huawei.com' \
--to=gur.stavi@huawei.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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 \
--cc=willemdebruijn.kernel@gmail.com \
/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).