From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 59B33ECAAD8 for ; Tue, 13 Sep 2022 16:40:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231626AbiIMQkH (ORCPT ); Tue, 13 Sep 2022 12:40:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48666 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230494AbiIMQjo (ORCPT ); Tue, 13 Sep 2022 12:39:44 -0400 Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8DF0953D01 for ; Tue, 13 Sep 2022 08:34:36 -0700 (PDT) Received: by mail-pf1-x42a.google.com with SMTP id y136so12126879pfb.3 for ; Tue, 13 Sep 2022 08:34:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date; bh=iJYXgpyoM4W9FbPBjOJQ/lNpfrEnMjCmpPpyo4wVWhM=; b=c1sxEX2Ib8z9hy2piq5AZbUupPNtEWY5GhTSAfoPwJ/iq27se+S5LxgASuB12efoH1 4NNYkKka+Bq5ElJjsyyQa2XSlhzb6rePXZS3R994skzfukmmXL9jWV9Fx+Zut/LxvNR+ 4GvEyBdFttKdxZtYt8DOF8cqihyOY/MhhwxL5/anWQdmoIi75r9W61EaEzN8dMoy8Kql XkCHv3gZcPCADXCPBO7G5nFxIirEnZWzSzEJawyygMDYJIfcGzPvMd2NJ+qqRaGAXN11 RBhCmwfRUtZm8fGNL2XRT+Bq+iq8Kj+Lu2ieuXUiG7ed6sAu539zldX5e5XtkDycEBXP UNqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date; bh=iJYXgpyoM4W9FbPBjOJQ/lNpfrEnMjCmpPpyo4wVWhM=; b=fw7EDMpVNMzzIYlsOurpgvhy3NgU5VC+rQsRdbOKj+BZdw6/LmiXit1/Rbf7/4rNsw hjTNeuO2pAmRLYiR6asnX7hHJm/9Sr5h+gV4AUbNSPUDTXvCiF9vJaKMOHQUxmX4mKBd ITtMYTOzBAluCmIjFRpeDajyLvx3YTz2rBDuroSH2Kw24VGgK+6mRX50lZnRqi1KIBdf soQDqWi47B/+c9UJr8/tbNxtVWskPnt+tPrQSNlt6vCiISx2GJI0NBEZ/Q+ceqaPpyY3 gOBEjVrziJHesSQulqSBxkXq9gf+KA9AybQxx7gWxa1cdkBXFjlI8pw/JViBYGLNRZIr 1cdA== X-Gm-Message-State: ACgBeo36iJwDGOiA3ZLVgw1ivt3sK5+0M/QZh/9djb8rj77pxLXxJ3wQ ZeS0TYiPwz5XRuleO/tBQsI= X-Google-Smtp-Source: AA6agR4tGi0xe39/HTg8WdhVQCob56kkLJi+uZY/nYmAp7olxRKbd6cTucqiqF5DIMPV9qOM3ek2JA== X-Received: by 2002:a63:3d3:0:b0:439:4408:246 with SMTP id 202-20020a6303d3000000b0043944080246mr2859412pgd.563.1663083202845; Tue, 13 Sep 2022 08:33:22 -0700 (PDT) Received: from [192.168.0.131] (198-27-223-25.fiber.dynamic.sonic.net. [198.27.223.25]) by smtp.gmail.com with ESMTPSA id d2-20020a170902cec200b0015e8d4eb219sm8624175plg.99.2022.09.13.08.33.21 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 13 Sep 2022 08:33:22 -0700 (PDT) Message-ID: Date: Tue, 13 Sep 2022 08:33:19 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [Bug] [Deadlock] Kernel thread deadlock in rfcomm socket release when connect interrupted Content-Language: en-US To: Peter Sutton , Thorsten Leemhuis Cc: Paul Menzel , Luiz Augusto von Dentz , linux-bluetooth@vger.kernel.org, regressions@lists.linux.dev References: <24e95c8b-dc05-0d00-50bb-58b71c5baf94@molgen.mpg.de> From: Desmond Cheong Zhi Xi In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-bluetooth@vger.kernel.org Hi all, On 13/9/22 08:20, Peter Sutton wrote: >> a fix for a deadlock for RFCOMM sk state change was posted last year already: >> >> https://lore.kernel.org/all/20211004180734.434511-1-desmondcheongzx@gmail.com/ >> >> It seems it never went anywhere, unless I'm missing something. Is that >> maybe the same problem or somehow related? > > I mentioned this on the Arch Linux Matrix channel. The `linux` package > maintainer said they had encountered the same and added the linked > patch to the Arch Linux kernel package but removed it because it > wasn't merged (which explains why my issue went way then came back). > Anyway, we compiled a 5.19.8 `linux` package with the patch (which > fixes my issue) and they said they'll add the patch back to the linux > package. Thanks for following up on this issue. I'd completely missed it until recently, and Luiz has suggested an alternative approach to fixing the problem here: https://lore.kernel.org/lkml/CABBYNZJxzA0U5bL6d0KtAkZw6yfUSNcpaH3Oh=xZFZdER8FCog@mail.gmail.com/ I'm planning to take a crack at it, but probably don't have the cycles for another week or so. Best wishes, Desmond