netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@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>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Shuah Khan <shuah@kernel.org>,
	david decotigny <decot@googlers.com>,
	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,
	stable@vger.kernel.org
Subject: Re: [PATCH net v3 3/3] selftest: netcons: create a torture test
Date: Mon, 8 Sep 2025 11:13:53 +0100	[thread overview]
Message-ID: <20250908101353.GC2015@horms.kernel.org> (raw)
In-Reply-To: <20250905-netconsole_torture-v3-3-875c7febd316@debian.org>

On Fri, Sep 05, 2025 at 10:25:09AM -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
> messages are being sent, as creating parallel targets.
> 
> The code launches three background jobs on distinct schedules:
> 
>  * Toggle netcons target every 30 iterations
>  * create and delete random_target every 50 iterations
>  * toggle iface every 70 iterations
> 
> This creates multiple concurrency sources that interact with netconsole
> states. This is good practice to simulate stress, and exercise netpoll
> and netconsole locks.
> 
> This test already found an issue as reported in [1]
> 
> Link: https://lore.kernel.org/all/20250901-netpoll_memleak-v1-1-34a181977dfc@debian.org/ [1]
> Signed-off-by: Breno Leitao <leitao@debian.org>
> Reviewed-by: Andre Carvalho <asantostc@gmail.com>

Reviewed-by: Simon Horman <horms@kernel.org>


      reply	other threads:[~2025-09-08 10:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 17:25 [PATCH net v3 0/3] net: netpoll: fix a memleak and create a selftest Breno Leitao
2025-09-05 17:25 ` [PATCH net v3 1/3] netpoll: fix incorrect refcount handling causing incorrect cleanup Breno Leitao
2025-09-08 10:12   ` Simon Horman
2025-09-08 20:47   ` Calvin Owens
2025-09-09  1:29     ` Jakub Kicinski
2025-09-09 20:17       ` Breno Leitao
2025-09-09 23:16         ` Jakub Kicinski
2025-09-10 14:12           ` Breno Leitao
2025-09-10 17:58             ` Jakub Kicinski
2025-09-10 18:50               ` Breno Leitao
2025-09-10  0:18       ` Jay Vosburgh
2025-09-10 14:07         ` Breno Leitao
2025-09-09 14:05     ` Breno Leitao
2025-09-10  0:40       ` Calvin Owens
2025-09-05 17:25 ` [PATCH net v3 2/3] selftest: netcons: refactor target creation Breno Leitao
2025-09-08 10:13   ` Simon Horman
2025-09-05 17:25 ` [PATCH net v3 3/3] selftest: netcons: create a torture test Breno Leitao
2025-09-08 10:13   ` Simon Horman [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=20250908101353.GC2015@horms.kernel.org \
    --to=horms@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=asantostc@gmail.com \
    --cc=calvin@wbinvd.org \
    --cc=davem@davemloft.net \
    --cc=decot@googlers.com \
    --cc=edumazet@google.com \
    --cc=efault@gmx.de \
    --cc=kernel-team@meta.com \
    --cc=kuba@kernel.org \
    --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 \
    --cc=stable@vger.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).