Return-path: Received: from wolverine01.qualcomm.com ([199.106.114.254]:20871 "EHLO wolverine01.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753541AbbHSLXs (ORCPT ); Wed, 19 Aug 2015 07:23:48 -0400 From: Kalle Valo To: Michal Kazior CC: , Subject: Re: [PATCH] ath10k: add missing mutex unlock on failpath References: <1439982533-26824-1-git-send-email-michal.kazior@tieto.com> Date: Wed, 19 Aug 2015 14:23:41 +0300 In-Reply-To: <1439982533-26824-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Wed, 19 Aug 2015 13:08:53 +0200") Message-ID: <87614ba5du.fsf@kamboji.qca.qualcomm.com> (sfid-20150819_132351_689351_A81599F8) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: linux-wireless-owner@vger.kernel.org List-ID: Michal Kazior writes: > Kernel would complain about leaving a held lock > after going back to userspace and would > subsequently deadlock. > > Fixes: e04cafbc38c7 ("ath10k: fix peer limit enforcement") > Reported-by: Dan Carpenter > Signed-off-by: Michal Kazior commit e04cafbc38c7 is currently going to 4.3-rc1 (it's in wireless-drivers-next currently). I think we should send this to 4.3 as well, right? -- Kalle Valo