All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jaehee <jhpark1013@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
	yoshfuji@linux-ipv6.org, dsahern@kernel.org, dsahern@gmail.com,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	shuah@kernel.org, linux-kernel@vger.kernel.org,
	aajith@arista.com, roopa@nvidia.com, roopa.prabhu@gmail.com,
	aroulin@nvidia.com, sbrivio@redhat.com
Subject: Re: [PATCH v3 net-next 0/3] net: ipv4/ipv6: new option to accept garp/untracked na only if in-network
Date: Sat, 16 Jul 2022 03:00:14 +0000	[thread overview]
Message-ID: <165794041466.22960.16853534349610766541.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1657755188.git.jhpark1013@gmail.com>

Hello:

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

On Wed, 13 Jul 2022 16:40:46 -0700 you wrote:
> The first patch adds an option to learn a neighbor from garp only if
> the source ip is in the same subnet as an address configured on the
> interface that received the garp message. The option has been added
> to arp_accept in ipv4.
> 
> The same feature has been added to ndisc (patch 2). For ipv6, the
> subnet filtering knob is an extension of the accept_untracked_na
> option introduced in these patches:
> https://lore.kernel.org/all/642672cb-8b11-c78f-8975-f287ece9e89e@gmail.com/t/
> https://lore.kernel.org/netdev/20220530101414.65439-1-aajith@arista.com/T/
> 
> [...]

Here is the summary with links:
  - [v3,net-next,1/3] net: ipv4: new arp_accept option to accept garp only if in-network
    https://git.kernel.org/netdev/net-next/c/e68c5dcf0aac
  - [v3,net-next,2/3] net: ipv6: new accept_untracked_na option to accept na only if in-network
    https://git.kernel.org/netdev/net-next/c/aaa5f515b16b
  - [v3,net-next,3/3] selftests: net: arp_ndisc_untracked_subnets: test for arp_accept and accept_untracked_na
    https://git.kernel.org/netdev/net-next/c/0ea7b0a454ca

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



      parent reply	other threads:[~2022-07-16  3:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-13 23:40 [PATCH v3 net-next 0/3] net: ipv4/ipv6: new option to accept garp/untracked na only if in-network Jaehee Park
2022-07-13 23:40 ` [PATCH v3 net-next 1/3] net: ipv4: new arp_accept option to accept garp " Jaehee Park
2022-07-13 23:40 ` [PATCH v3 net-next 2/3] net: ipv6: new accept_untracked_na option to accept na " Jaehee Park
2022-07-18  8:35   ` Nicolas Dichtel
2022-07-18 16:58     ` Jaehee
2022-07-13 23:40 ` [PATCH v3 net-next 3/3] selftests: net: arp_ndisc_untracked_subnets: test for arp_accept and accept_untracked_na Jaehee Park
2022-07-16  3:00 ` 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=165794041466.22960.16853534349610766541.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aajith@arista.com \
    --cc=aroulin@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=jhpark1013@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=roopa.prabhu@gmail.com \
    --cc=roopa@nvidia.com \
    --cc=sbrivio@redhat.com \
    --cc=shuah@kernel.org \
    --cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.