From: Jakub Kicinski <kuba@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-kselftest@vger.kernel.org, asantostc@gmail.com,
efault@gmx.de, calvin@wbinvd.org, kernel-team@meta.com
Subject: Re: [PATCH net-next v2 0/2] net: selftest: Introduce netconsole torture test
Date: Thu, 4 Sep 2025 14:59:25 -0700 [thread overview]
Message-ID: <20250904145925.101e2091@kernel.org> (raw)
In-Reply-To: <20250904-netconsole_torture-v2-0-5775ed5dc366@debian.org>
On Thu, 04 Sep 2025 11:00:39 -0700 Breno Leitao wrote:
> Create a netconsole test that puts a lot of pressure on the netconsole
> list manipulation. Do it by creating dynamic targets and deleting
> targets while messages are being sent. Also put interface down while the
>
> In order to do it, refactor create_dynamic_target(), so it can be used to
> create random targets in the torture test.
You either have to post it in the same series as the fix, or wait for
the fix to be present in net-next. Without your pending fix this will
obviously not pass thru the CI :/
next prev parent reply other threads:[~2025-09-04 21:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 18:00 [PATCH net-next v2 0/2] net: selftest: Introduce netconsole torture test Breno Leitao
2025-09-04 18:00 ` [PATCH net-next v2 1/2] selftest: netcons: refactor target creation Breno Leitao
2025-09-04 18:00 ` [PATCH net-next v2 2/2] selftest: netcons: create a torture test Breno Leitao
2025-09-05 11:27 ` Andre Carvalho
2025-09-04 21:59 ` Jakub Kicinski [this message]
2025-09-05 17:27 ` [PATCH net-next v2 0/2] net: selftest: Introduce netconsole " Breno Leitao
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=20250904145925.101e2091@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=calvin@wbinvd.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=efault@gmx.de \
--cc=kernel-team@meta.com \
--cc=leitao@debian.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 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.