From f83f92fd5e8f53114eb4e4149c19f2c4d7fddc78 Mon Sep 17 00:00:00 2001 From: Dmitry Vyukov Date: Fri, 20 Dec 2019 14:19:12 +0100 Subject: tools/syz-check: inject description compilation warnings Currently we print them as part of `make genereate`, but nobody reads them, too much output each time. Don't print them in `make generate` and instead print in syz-check, the warn files are a good mechanism to handle "known warnings". --- sys/linux/vusb.txt.warn | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'sys/linux/vusb.txt.warn') diff --git a/sys/linux/vusb.txt.warn b/sys/linux/vusb.txt.warn index 34cf6e5e3..ad9effbce 100644 --- a/sys/linux/vusb.txt.warn +++ b/sys/linux/vusb.txt.warn @@ -1,6 +1,10 @@ +len target configs refer to an array with variable-size elements (do you mean bytesize?) +len target interfaces refer to an array with variable-size elements (do you mean bytesize?) +len target endpoints refer to an array with variable-size elements (do you mean bytesize?) struct vusb_connect_string_descriptor: no corresponding struct in kernel struct vusb_descriptors: no corresponding struct in kernel struct vusb_responses: no corresponding struct in kernel +len target caps refer to an array with variable-size elements (do you mean bytesize?) struct usb_wireless_cap_descriptor: no corresponding struct in kernel struct usb_ext_cap_descriptor: bad number of fields: syz=7 kernel=4 field usb_ext_cap_descriptor.bmAttributes1/bmAttributes: bad bit size/offset: syz=8/0 kernel=0/0 -- cgit mrf-deployment