Hi,
I think I'm hitting a lot of false positives regarding spin locks when
compiling a kernel with at91_dt_defconfig. For example:
CHECK drivers/usb/gadget/atmel_usba_udc.c
/home/alex/linux/drivers/usb/gadget/atmel_usba_udc.c:623 usba_ep_enable() warn: inconsistent returns 'spin_lock:&udc->lock'.
Locked on: line 531
line 560
line 569
Unlocked on: line 623
/home/alex/linux/drivers/usb/gadget/atmel_usba_udc.c:740 queue_dma() warn: inconsistent returns 'spin_lock:&udc->lock'.
Locked on: line 709
line 714
Unlocked on: line 740
/home/alex/linux/drivers/usb/gadget/atmel_usba_udc.c:786 usba_ep_queue() warn: inconsistent returns 'spin_lock:&udc->lock'.
Locked on: line 757
line 767
Unlocked on: line 786
/home/alex/linux/drivers/usb/gadget/atmel_usba_udc.c:917 usba_ep_set_halt() warn: inconsistent returns 'spin_lock:&udc->lock'.
Locked on: line 888
line 893
Unlocked on: line 917
/home/alex/linux/drivers/usb/gadget/atmel_usba_udc.c:1807 atmel_usba_start() error: double unlock 'spin_lock:&udc->lock'
I'm using make C=1 CHECK="/home/alex/smatch/smatch --full-path
-p=kernel" to compile, smatch is at 845cc11365bb
Is there anything I am doing wrong? Or anything I can do to silence
those warnings?
Regards,
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe smatch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
