Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp883550rwi; Wed, 19 Oct 2022 04:17:16 -0700 (PDT) X-Google-Smtp-Source: AMsMyM768cg6jhfOYEPKOasnvhM+ttfHsDNTn23vSjh3E7n1o9XvYNcbpKGtGn+I7pHRwy8AfaP0 X-Received: by 2002:a17:902:ce09:b0:178:bb78:49a5 with SMTP id k9-20020a170902ce0900b00178bb7849a5mr7936332plg.100.1666178235913; Wed, 19 Oct 2022 04:17:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666178235; cv=none; d=google.com; s=arc-20160816; b=fqn1FGYPcqpPMSll5o+UK8nHDVUx2mqiIRq2kFSReEoIG3382QooHYufoFOQ+dqoBt X85J8/9/i8VbADY8AIkCms2RciLkMmiWRrMqkgOi8deRxr/SNL93+oFq0tSSzYtGLqdk jZU/tVRW3RjRna1eJtTI5hySuCixU+LaIFkiqaByoXjsliDQYet8RUhycTly9+eIsqfb iQHcGo/Kw6j6S0rQ9qOZ3Rfu/VER/NyW+3Tx26+ydr1Zc98S69x1jRd9xw+uFVCpVYG7 nLE54qMNbnJE98v0ofGlx2z0JUE582iG0MntdYiRzlGtsXWvfO+uPmnyxeavdmk8h0tL geMw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=JpdVq4gNkwurGSmqYH9Aof38YZcYgwm7+YigtH/JSMI=; b=mgEZhm7fIRqeluyZMXfyjDwTcmuXi/4aJAbkrOvP8auW9ajTJoDGJOK313Nun1mjBf hBSuYnvku7IRBI36+xInmbpQmgT+R6CjCWRoL6r+ZoRLPTLiQG0Mvlb+lKExSTMa32Ow Et+zK5sU2fNrZUnVkqrAO2kgcPzP0/+0sv4qYufzIaV5fuZyuX7ixkKedN7sHwkC93cw kWmJiBta5qwaUA/wjEJ7uQ6P47t9sfa2BKB0DkwSZCtlptvz/MmyAGk1LoPzNRMhRvCd 7v+bYE56IQOPOY2ggDitVhCMOwjL2/jur1HofqTUFzmKm71O9X6DfpAirjb1ePdJx2yv E6dg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=wwmUABvm; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id jj5-20020a170903048500b00179f69eae64si18941294plb.620.2022.10.19.04.17.04; Wed, 19 Oct 2022 04:17:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=wwmUABvm; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232514AbiJSKml (ORCPT + 99 others); Wed, 19 Oct 2022 06:42:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231986AbiJSKlq (ORCPT ); Wed, 19 Oct 2022 06:41:46 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 45A5A27DEB; Wed, 19 Oct 2022 03:19:37 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 19F4DB822E1; Wed, 19 Oct 2022 08:51:24 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7B977C433C1; Wed, 19 Oct 2022 08:51:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1666169482; bh=C6CwbD+x4Djmkf1hfONC+CIP9Mm3gn2aJ3WQUw0pJs4=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=wwmUABvmBIrj2jHgzEuKzwjTuHfGkUBB5k9K4ENhAiCc4RsTbVv10T49UqPu3Dhhh Edh6aRNYHRpj+k1C6/ZTDvKlDRCkAdfmzOK012dga7JWoIt2lEHryYPd+sgoTXGScQ hyCXYP/nCS7WgiHScdHcynufDoDELzAxwgWalUhM= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, Luiz Augusto von Dentz , Sasha Levin Subject: [PATCH 6.0 293/862] Bluetooth: RFCOMM: Fix possible deadlock on socket shutdown/release Date: Wed, 19 Oct 2022 10:26:20 +0200 Message-Id: <20221019083302.963385999@linuxfoundation.org> X-Mailer: git-send-email 2.38.0 In-Reply-To: <20221019083249.951566199@linuxfoundation.org> References: <20221019083249.951566199@linuxfoundation.org> User-Agent: quilt/0.67 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-7.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Luiz Augusto von Dentz [ Upstream commit 812e92b824c1db16c9519f8624d48a9901a0d38f ] Due to change to switch to use lock_sock inside rfcomm_sk_state_change the socket shutdown/release procedure can cause a deadlock: rfcomm_sock_shutdown(): lock_sock(); __rfcomm_sock_close(): rfcomm_dlc_close(): __rfcomm_dlc_close(): rfcomm_dlc_lock(); rfcomm_sk_state_change(): lock_sock(); To fix this when the call __rfcomm_sock_close is now done without holding the lock_sock since rfcomm_dlc_lock exists to protect the dlc data there is no need to use lock_sock in that code path. Link: https://lore.kernel.org/all/CAD+dNTsbuU4w+Y_P7o+VEN7BYCAbZuwZx2+tH+OTzCdcZF82YA@mail.gmail.com/ Fixes: b7ce436a5d79 ("Bluetooth: switch to lock_sock in RFCOMM") Signed-off-by: Luiz Augusto von Dentz Signed-off-by: Sasha Levin --- net/bluetooth/rfcomm/sock.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/net/bluetooth/rfcomm/sock.c b/net/bluetooth/rfcomm/sock.c index 4bf4ea6cbb5e..21e24da4847f 100644 --- a/net/bluetooth/rfcomm/sock.c +++ b/net/bluetooth/rfcomm/sock.c @@ -902,7 +902,10 @@ static int rfcomm_sock_shutdown(struct socket *sock, int how) lock_sock(sk); if (!sk->sk_shutdown) { sk->sk_shutdown = SHUTDOWN_MASK; + + release_sock(sk); __rfcomm_sock_close(sk); + lock_sock(sk); if (sock_flag(sk, SOCK_LINGER) && sk->sk_lingertime && !(current->flags & PF_EXITING)) -- 2.35.1