On Wed, Oct 21, 2026 at 1:23 PM Jakub Kicinski <[email protected]> wrote: > > On Tue, 20 Oct 2026 23:17:34 -0700 Mina Almasry wrote: > > But on the other hand the test coverage is nice, and maybe one day if > > we add enough devmem support in netdevsim we'll be able to fuzz the > > data path or something. Is there a way to get the best of both worlds? > > Like put a comment on top of netdevsim that this is test simulator > > device and any missing functionality and/or bugs in it should be > > medium criticality max or something? Or is it too much trouble and I > > should drop the netdevsim support and tests? > > I already strip Fixes tags and apply the patches to net-next. > But it's still a burden. If you're signing up to fix the issues / > review the slop we can try.
I'm more than happy to help but I'm not sure what you have specifically in mind. What I was going to do is put a comment/readme in drivers/net/netdevsim with a note to sashiko and LLMs, "this is a netdev simulator, used for testing; do not call out missing or incomplete functionality as bugs." And then hope that the LLMs and sashiko pick the directive. If not, I can tell patch submitters to ignore sashiko code review bug findings in netdevsim. Is that sufficient, or do you need something else from me? And we can always revert the added devmem supprot in netdev sim if it becomes an issue. -- Thanks, Mina
