On Tue, 02 Sep 2025 09:33:33 -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.
Oh, when you said "selftest will be posted later" in the fix I thought you meant days, not hours later :) It's better if the fix and test are in one series. Better for backports, and it avoid situations like last night when the fix was already dropped from pw but this test was still running (and crashing the kernel).
Regarding the test, I think it makes sense. Tho is there a way we can reuse more of the existing code? Do you write all these scripts by hand or get AI to write them? I was hoping you'd add more tests relating to bonding. To confirm bonding still works. And as I mentioned I think bonding is still a bit buggy if we "propagate" multiple nps and then remove them out of order..