linux-kernel - Re: lockdep warning in urb.c:363 usb_submit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200324104610.pqdtaocg6qctlnqv@e107158-lin>
Date:   Tue, 24 Mar 2020 10:46:12 +0000
From:   Qais Yousef <qais.yousef@....com>
To:     Oliver Neukum <oneukum@...e.de>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: lockdep warning in urb.c:363 usb_submit_urb

On 03/24/20 10:08, Oliver Neukum wrote:
> Am Montag, den 23.03.2020, 17:29 +0000 schrieb Qais Yousef:
> > Hi Oliver
> 
> Hi,
> 
> > First time I use dynamic debugging, hopefully I've done correctly.
> 
> I am afraid not.
> 
> > 	echo "file drivers/usb/* +p" > /sys/kernel/debug/dynamic_debug/control
> 
> Overkill but correct. +mpf would be even better
> 
> > 	$REPRODUCE
> 
> Good
> 
> > 	cat /sys/kernel/debug/dynamic_debug/control | grep usb > usb.debug
> 
> No.
> 
> /sys/kernel/debug/dynamic_debug/control holds the collection of the
> messages that may be triggered, but it does not tell you which messages
> are triggered and in which order. The triggered messages end up
> in syslog. So you would use 'dmesg'
> I am afraid you redid the test correctly and then threw away the
> result.
> Could you redo it and just attach the output of dmesg?
> 
> 	Sorry

I should have stuck to what I know then. I misread the documentation. Hopefully
the attached looks better. I don't see the new debug you added emitted.

Thanks

--
Qais Yousef

View attachment "usb.dmesg" of type "text/plain" (56460 bytes)