From: Simon Horman <horms@kernel.org>
To: Aaron Conole <aconole@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Pravin B Shelar <pshelar@ovn.org>,
dev@openvswitch.org, Ilya Maximets <i.maximets@ovn.org>,
Eelco Chaudron <echaudro@redhat.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, andy zhou <azhou@ovn.org>
Subject: Re: [PATCH net v2 2/2] selftests: openvswitch: Add validation for the recursion test
Date: Thu, 8 Feb 2024 11:30:12 +0000 [thread overview]
Message-ID: <20240208113012.GH1435458@kernel.org> (raw)
In-Reply-To: <20240207132416.1488485-3-aconole@redhat.com>
On Wed, Feb 07, 2024 at 08:24:16AM -0500, Aaron Conole wrote:
> Add a test case into the netlink checks that will show the number of
> nested action recursions won't exceed 16. Going to 17 on a small
> clone call isn't enough to exhaust the stack on (most) systems, so
> it should be safe to run even on systems that don't have the fix
> applied.
>
> Signed-off-by: Aaron Conole <aconole@redhat.com>
> ---
> v1->v2: Used a slightly more portable io redirection semantic for the
> clone() flow test case.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-02-08 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 13:24 [PATCH net v2 0/2] net: openvswitch: limit the recursions from action sets Aaron Conole
2024-02-07 13:24 ` [PATCH net v2 1/2] net: openvswitch: limit the number of " Aaron Conole
2024-02-08 11:29 ` Simon Horman
2024-02-07 13:24 ` [PATCH net v2 2/2] selftests: openvswitch: Add validation for the recursion test Aaron Conole
2024-02-08 11:30 ` Simon Horman [this message]
2024-02-09 21:00 ` [PATCH net v2 0/2] net: openvswitch: limit the recursions from action sets 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=20240208113012.GH1435458@kernel.org \
--to=horms@kernel.org \
--cc=aconole@redhat.com \
--cc=azhou@ovn.org \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.org \
--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).