Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933965AbbKSJLH (ORCPT ); Thu, 19 Nov 2015 04:11:07 -0500 Received: from mx2.suse.de ([195.135.220.15]:36059 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933849AbbKSJKU (ORCPT ); Thu, 19 Nov 2015 04:10:20 -0500 Date: Thu, 19 Nov 2015 10:10:19 +0100 (CET) From: Jiri Kosina X-X-Sender: jkosina@pobox.suse.cz To: Ioan-Adrian Ratiu cc: Josh Cartwright , pinglinux@gmail.com, linux-usb@vger.kernel.org, linux-input@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] hid: usbhid: hid-core: fix recursive deadlock In-Reply-To: <20151119084743.08d11238@adipc> Message-ID: References: <1447874755-8673-1-git-send-email-adi@adirat.com> <20151118230544.5c6f0c26@adipc> <20151118235856.GA30351@jcartwri.amer.corp.natinst.com> <20151119084743.08d11238@adipc> User-Agent: Alpine 2.00 (LNX 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1090 Lines: 35 On Thu, 19 Nov 2015, Ioan-Adrian Ratiu wrote: > First part of lockdep report: > http://imgur.com/clLsCWe > > Second part: > http://imgur.com/Wa2PzRl > > Here are some printk's of mine while reproducing + debugging the issue: > http://imgur.com/SETOHT7 So the real problem is that Intuos driver is calling hid_hw_request() (which tries to grab the lock in usbhid_submit_report()) while handling the CTRL IRQ (lock gets acquired there). So the proper way to fix seems to be delaying the scheduling of the proximity read event in wacom_intuos_inout() to workqueue. > I'll continue to research this more in depth, but progress is slow > because I don't have much time, I'm doing this in my spare time because > it's my girlfriend's tablet. Oh, now I understand the level of severity of this bug! :-) Thanks, -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/