Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp4417121ioa; Wed, 27 Apr 2022 03:29:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy2tblJ9hmVN9vbUZujuppPFYmxzKkbSxVSamDI6XJz2dAlBDO3OMoUqSgwp2wNaJ5RYmiD X-Received: by 2002:a17:902:ca92:b0:15d:2b3d:641a with SMTP id v18-20020a170902ca9200b0015d2b3d641amr10577489pld.168.1651055354307; Wed, 27 Apr 2022 03:29:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651055354; cv=none; d=google.com; s=arc-20160816; b=SrZYn+SkDXBlwRVmtn+B+N4aaVVN4BsC3xwNwA6aM0U02ygeVotGrEzWfJ9gYnPdLi NsaoXlyRHOVtoWJ4OjpSjH+xCYYZbRfaquNcmOQGckDOP2IewqVlcZU1lgy1ASXNYTM1 +FeMj+bTk8ir5U2fNPNXiyzpGGoWWf+dwylZTKzTJ6toecKEIf/XuCuNeUNfyiH2gQ6P 6hLe9yNSajyjWgbt6I/AdGUDVqLnhQTMKy4cct9bHGJ/xOyEhSsmOKJ4jSF3HQ8ehmKO QurZNE8L2GULTTdNNJXLQHLiCbqNEH8+GwDfuKN38y1D38zuwREZF+YykTo8IsOqOTWQ QxDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:dkim-signature; bh=oEWQcep1X9f8aeHfmFWOpt8FIWNWJQ/z5b28ytC9iM4=; b=taJywK/hemHUqAn2hkqVDBa2YQ4qI4w3mEZRkAMXNHfNW9QWZjEa0X1fo30AYFOi+r 66f/Bgkb+KZRtnqJMBhTevvcTGpEsJnJpOROWWrsxlXLqAmCVaC+7JOPa69HIKj7lriI f52glvvXIVtK1Nd5/IZX6bYTUjY9AXX+VstehiaF+crUgPloqFbakK9Om4S78R04kRKa 2MqbPBHSPTWWdc+lXlx14yyiPGx7pTNgovGCyir7Wp9s97xcRsiJXkLkkrpH8kKP1Yuc tpBnqGP/ZMqwMbv5I+dbb7SKrPeTDViau68fSKoNALdkxlOCdn7C5yyjyXpcm0HTLup/ lTWg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@hartkopp.net header.s=strato-dkim-0002 header.b=Gle9f4+7; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id q6-20020a170902f78600b00158eb28cb9dsi1253010pln.254.2022.04.27.03.29.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Apr 2022 03:29:14 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@hartkopp.net header.s=strato-dkim-0002 header.b=Gle9f4+7; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 5BD18282B73; Wed, 27 Apr 2022 02:44:42 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349580AbiDZTQd (ORCPT + 99 others); Tue, 26 Apr 2022 15:16:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56314 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233575AbiDZTQc (ORCPT ); Tue, 26 Apr 2022 15:16:32 -0400 Received: from mo4-p01-ob.smtp.rzone.de (mo4-p01-ob.smtp.rzone.de [85.215.255.50]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A27F319D493; Tue, 26 Apr 2022 12:13:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1651000375; s=strato-dkim-0002; d=hartkopp.net; h=In-Reply-To:From:References:Cc:To:Subject:Date:Message-ID:Cc:Date: From:Subject:Sender; bh=oEWQcep1X9f8aeHfmFWOpt8FIWNWJQ/z5b28ytC9iM4=; b=Gle9f4+77olBM8T1Dg+EtcQ3ABOx2sXkoWDUbHvGXHzqgWZZraj5mCu1e1WIgc432n mZe3DdFURB3gP8SxkHT63006HZMWtgIzFIyXIsWQ372PL4VJlgmkrEEtz2n6GJOEGHmL j2+S7AEoUvotBFcaetYlFrS2+XyNRlzFgUPAQ64daplpDTGRy3AaDH9nubcSDyjxDdxK j/71Pzw8McYvUXX2Vnz8cTFA0ZxK8N/dmhKt+oe8JCuY10dY+s1dPPg3+iYY08DEWBCo Uag2nJuwR+KfU5aB8vVcyOJIwSgX79tGQrGZManG97a9LAqh2JVlzJC9UP7Gvb7KHE6M MTSA== Authentication-Results: strato.com; dkim=none X-RZG-AUTH: ":P2MHfkW8eP4Mre39l357AZT/I7AY/7nT2yrDxb8mjG14FZxedJy6qgO1qCHSa1GLptZHusx3hdBqPeOug2krLFRKxw==" X-RZG-CLASS-ID: mo00 Received: from [IPV6:2a00:6020:1cff:5b04::b82] by smtp.strato.de (RZmta 47.42.2 AUTH) with ESMTPSA id 4544c9y3QJCsKBL (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256 bits)) (Client did not present a certificate); Tue, 26 Apr 2022 21:12:54 +0200 (CEST) Message-ID: Date: Tue, 26 Apr 2022 21:12:48 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0 Subject: Re: [PATCH net] drivers: net: can: Fix deadlock in grcan_close() Content-Language: en-US To: Duoming Zhou , linux-kernel@vger.kernel.org Cc: wg@grandegger.com, mkl@pengutronix.de, davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com, linux-can@vger.kernel.org, netdev@vger.kernel.org References: <20220425042400.66517-1-duoming@zju.edu.cn> From: Oliver Hartkopp In-Reply-To: <20220425042400.66517-1-duoming@zju.edu.cn> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.8 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,NICE_REPLY_A,RDNS_NONE,SPF_HELO_NONE autolearn=unavailable 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 On 25.04.22 06:24, Duoming Zhou wrote: > There are deadlocks caused by del_timer_sync(&priv->hang_timer) > and del_timer_sync(&priv->rr_timer) in grcan_close(), one of > the deadlocks are shown below: > > (Thread 1) | (Thread 2) > | grcan_reset_timer() > grcan_close() | mod_timer() > spin_lock_irqsave() //(1) | (wait a time) > ... | grcan_initiate_running_reset() > del_timer_sync() | spin_lock_irqsave() //(2) > (wait timer to stop) | ... > > We hold priv->lock in position (1) of thread 1 and use > del_timer_sync() to wait timer to stop, but timer handler > also need priv->lock in position (2) of thread 2. > As a result, grcan_close() will block forever. > > This patch extracts del_timer_sync() from the protection of > spin_lock_irqsave(), which could let timer handler to obtain > the needed lock. > > Signed-off-by: Duoming Zhou > --- > drivers/net/can/grcan.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/drivers/net/can/grcan.c b/drivers/net/can/grcan.c > index d0c5a7a60da..1189057b5d6 100644 > --- a/drivers/net/can/grcan.c > +++ b/drivers/net/can/grcan.c > @@ -1102,8 +1102,10 @@ static int grcan_close(struct net_device *dev) > > priv->closing = true; > if (priv->need_txbug_workaround) { > + spin_unlock_irqrestore(&priv->lock, flags); > del_timer_sync(&priv->hang_timer); > del_timer_sync(&priv->rr_timer); > + spin_lock_irqsave(&priv->lock, flags); It looks weird to unlock and re-lock the operations like this. This breaks the intended locking for the closing process. Isn't there any possibility to e.g. move that entire if-section before the lock? > } > netif_stop_queue(dev); > grcan_stop_hardware(dev); Regards, Oliver