On Thu, Dec 19, 2019 at 10:35 AM Dmitry Vyukov <dvyukov@xxxxxxxxxx> wrote: > > Is this precise enough for race > > condition bugs? > > It's finding lots of race conditions provoked bugs (I would say it's > the most common cause of kernel bugs). I meant -- are the reproducers it makes precise enough to retrigger network-level race conditions? > Well, you are missing that wireguard is not the only subsystem > syzkaller tests (in fact, it does not test it at all) and there are > 3000 other subsystems :) Oooo! Everything is tested at the same time. I understand now; that makes a lot more sense. I'll look into splitting out the option, as you've asked. Note, though, that there are currently only three spots that have the "extra checks" at the moment, and one of them can be optimized out by the compiler with aggressive enough inlining added everywhere. The other two will result in an immediately corrupted stack frame that should be caught immediately by other things. So for now, I think you can get away with turning the debug option off, and you won't be missing much from the "extra checks", at least until we add more. That's exciting about syzcaller having at it with WireGuard. Is there some place where I can "see" it fuzzing WireGuard, or do I just wait for the bug reports to come rolling in? Jason
