summaryrefslogtreecommitdiff
path: root/drivers/misc/mic/scif/scif_dma.c
diff options
context:
space:
mode:
authorAndrey Konovalov <andreyknvl@google.com>2020-10-16 16:57:45 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-10-28 15:10:54 +0300
commitaee9ddb1d3718d3ba05b50c51622d7792ae749c9 (patch)
treedbfc82c0703ddbb03c628f0246746ff8c0b6dc0e /drivers/misc/mic/scif/scif_dma.c
parentecbb4dac5f6ccbc5443609ec72021994b662e06d (diff)
downloadlinux-aee9ddb1d3718d3ba05b50c51622d7792ae749c9.tar.xz
kcov, usb: only collect coverage from __usb_hcd_giveback_urb in softirq
Currently there's a KCOV remote coverage collection section in __usb_hcd_giveback_urb(). Initially that section was added based on the assumption that usb_hcd_giveback_urb() can only be called in interrupt context as indicated by a comment before it. This is what happens when syzkaller is fuzzing the USB stack via the dummy_hcd driver. As it turns out, it's actually valid to call usb_hcd_giveback_urb() in task context, provided that the caller turned off the interrupts; USB/IP does exactly that. This can lead to a nested KCOV remote coverage collection sections both trying to collect coverage in task context. This isn't supported by KCOV, and leads to a WARNING. Change __usb_hcd_giveback_urb() to only call kcov_remote_*() callbacks when it's being executed in a softirq. As the result, the coverage from USB/IP related usb_hcd_giveback_urb() calls won't be collected, but the WARNING is fixed. A potential future improvement would be to support nested remote coverage collection sections, but this patch doesn't address that. Reviewed-by: Dmitry Vyukov <dvyukov@google.com> Acked-by: Marco Elver <elver@google.com> Signed-off-by: Andrey Konovalov <andreyknvl@google.com> Link: https://lore.kernel.org/r/f3a7a153f0719cb53ec385b16e912798bd3e4cf9.1602856358.git.andreyknvl@google.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/misc/mic/scif/scif_dma.c')
0 files changed, 0 insertions, 0 deletions