On Tue, Dec 18, 2018 at 4:40 AM Stefano Brivio <sbri...@redhat.com> wrote: > Not as far as I know. The selftests checking this path, by design, only > use supported configurations, they don't forge packets. > > Maybe it would be nice to have a semi-automated way to isolate and > describe/name specific conditions found by syzbot via fuzzing and turn > those into tests that are then repeated periodically. I'm not sure how > that would look like, but I think it's still more maintainable than a > pile of C reproducers with forged packets in selftests/net. > > Eric, Cong, Xin, as you also recently fixed a nice deal of similar cases > reported by syzbot, what do you think? Did you ever feel the need to > turn a syzbot reproducer into a regression test case?
I think it is a very good idea to archive these C reproducers in tools/testing/selftests/. After this is done, kbuild bot could do these regression tests, no longer need to bother syzbot to run them again. :) Thanks.
