Hello Lukas, Sorry for the late reply. On Thu, 21 Jul 2022 16:05:01 +0530 Lukas Bulwahn <lukas.bulwahn@xxxxxxxxx> wrote: > Siddh, > > I had a look at the Bug report above. Currently, we do not have any > syzkaller or C reproducer to confirm that the bug was actually fixed. > > Now, that you have a supposed fix for the issue: > Can you write a 'stress test' and (qemu) setup script that eventually > makes that bug trigger (e.g., if we run the stress test for two or > three days it will eventually trigger)? Then, we can also use that to > confirm that your patch fixes the issue (beyond the normal sanity code > review). > > This is certainly something you can do on your side to move this patch > forward, and other developers with testing infrastructure can pick up > and confirm your tests and results independently. I have been intermittently looking about this for the past few days. Since such test creation is new to me, I am stuck at how to go about calling the requisite function. What I have gathered is that I need to use the netlink API or related tool and issue the scan and recieve commands. Since qemu by default doesn't have a WiFi interface setup by default, I was looking at simulation and came across the mac80211_hwsim module. After building the kernel it, I tried using `iw` command for scanning with the two phy simulated devices, but I seem to hit a deadend due to not being able to properly use them for the task at hand. Do you have any resources or/and examples on such "stress tests"? > I hope this helps, otherwise you will just need to have some patience. > > Best regards, > > Lukas Eric had replied to me on the original email soon after, and I have sent a v2. Though, I still want to see how people go about making the tests, so any resources for further exploring will be useful. Thanks, Siddh
