Dmitry Vyukov

Maybe you can suggest some suitable description file that is reachable in VMs and that is missing in our current descriptions?

These seem to have the same issue: no ioctls or only inptr's as arguments and unrelated devices merged into the same resource type. I think ioctl argument types are critical,...

Ah, I see. One common approach for such issues is checking in auto-generated results after any changes, then diffs highlight any unintentional changes. We use this for kernel configs, descriptions...

I see there are lots of improvements! Nice! I've tried one file and it does not compile: ``` syz_describe_drivers_block_mtip32xx_mtip32xx_c_amd64.txt:19:1: resource fd_11113595003055145101_fd can't be created (never mentioned as a syscall return...

That commit was supposed to only update the issue. It's not fixed yet.

And most bugs abort the kernel. Also not clear what are "USB bugs". If kernel could detect "USB bugs", it could dump the necessary info on panics.

Would it work if kernel would log attach/detach events? This would be useful for any kernel testing system.

Is it guaranteed to print the info before kernel crashes?

lsusb comes from usbutils package and buildroot has BR2_PACKAGE_USBUTILS. I don't have usbmon installed and `apt-cache search usbmon` does not give me anything.

Interesting. What does it take to enable KDB? How can it be communicated? Does it have any other side-effects?