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 X-Spam-Level: X-Spam-Status: No, score=-3.2 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HK_RANDOM_FROM,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6F76CC433EF for ; Mon, 13 Sep 2021 15:05:14 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 504F860240 for ; Mon, 13 Sep 2021 15:05:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346773AbhIMPGY (ORCPT ); Mon, 13 Sep 2021 11:06:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:52666 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346719AbhIMPGJ (ORCPT ); Mon, 13 Sep 2021 11:06:09 -0400 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 81D83C014DB0 for ; Mon, 13 Sep 2021 06:39:20 -0700 (PDT) Received: by mail-ej1-x62d.google.com with SMTP id ho42so21137162ejc.9 for ; Mon, 13 Sep 2021 06:39:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=xNtQ1ARmV5D+fRgpV2FNt+0W8ArnaPaQlO7L2peESTE=; b=RvxWi5/tXCdLO7VqGQL3V9uryQuY7gHxKhcjKavKZ+Pyj1nKnLSEfRBRLyR+ho1P0j j6xAGprbt/YeW3sGKbdIpwmUKQHm61eevNX4ipY0UX4wjWp8v4NjQ+22NbcqHk36RLhI 3xQQCWOZXwX3NkC5qEjbocVVwy9t5nKA5bhdfzWZPjusJtsV2CMSySLZH52EQj8B6mwe OY3ii4BH9Djyyvl/gLNkzpDwvgGhXTc5M2F3hU0Rt3WOZKnKe2H/fziX1D+UeRsK0Mit cdLToHwhiaiFEfjIgYxjhnqHNGJZN/FACz8VPKp8qDyCBGilgjBRHt6MhKc7yMAO3Bmc 36Qw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=xNtQ1ARmV5D+fRgpV2FNt+0W8ArnaPaQlO7L2peESTE=; b=JrNzk/BzJ4DbWUb97U/XneHHk9FhzjpsVRyKWqHYmZPDOY0W5zA77uILk2+w1xsM7Y CibChYWidaEkOnNEJDX3K45xsskm28bCdUoM9eRWzuxodm9l69rcOC9VUyTodzuetJIF 2rlLHNRhvu6vkUMdyKoAVV5u/oQAlYPEu5vHp7nngzxNyIVl0AvRMdf6ORs9KxkBHbh8 Eo9CTzwTvjn6ot5w4PwZM8vNZwoSnz3x4bEyMYctzVF1l4S9LhCz/Z+IsuHpGffcC67Y h4xVqr0pmmjDPoMAbhhk606Fvdx+5LBe47zShVksEGZzUB4EewVOhnKQwSxxKgf+u4F+ ow9Q== X-Gm-Message-State: AOAM532zufmTAiR0GjKHE5HyCamsEpQnkhVz6l0w3OuopPtql/DYXCZ0 OTF5JHr1XT7VG/TFI2IyE/1c2WvupV4= X-Google-Smtp-Source: ABdhPJyht4ntrEK4VNA0hVeDb0PzwJk+HkwTNDL1GhPLqBX2U+F/hHPKuTs7dFjpfVLAv4oOVw5GOg== X-Received: by 2002:a17:906:318c:: with SMTP id 12mr12950913ejy.28.1631540359147; Mon, 13 Sep 2021 06:39:19 -0700 (PDT) Received: from agape.jhs ([5.171.73.21]) by smtp.gmail.com with ESMTPSA id dj8sm2818163edb.53.2021.09.13.06.39.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 13 Sep 2021 06:39:18 -0700 (PDT) Date: Mon, 13 Sep 2021 15:39:16 +0200 From: Fabio Aiuto To: Hans de Goede Cc: gregkh@linuxfoundation.org, Larry.Finger@lwfinger.net, linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org Subject: Re: [PATCH] staging: rtl8723bs: protect sleepq_len access by sleep_q.lock Message-ID: <20210913133915.GA1414@agape.jhs> References: <20210913130346.2390-1-fabioaiuto83@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Hans, On Mon, Sep 13, 2021 at 03:24:44PM +0200, Hans de Goede wrote: > Hi Fabio, > > > Note that sleep_q.lock is already taken inside > > rtw_free_xmitframe_queue so we just wrap sleepq_len > > access. > > > > Moved pxmitpriv->lock after sleep_q.lock release to > > avoid locks nesting. > > rtw_free_xmitframe_queue(pxmitpriv, &psta->sleep_q); > > + spin_lock_bh(&psta->sleep_q.lock); > > AFAICT this needs to be above the rtw_free_xmitframe_queue() ? as I wrote on the changelog, the sleep_q.lock is already taken inside rtw_free_xmitframe_queue. If I put the sleep_q.lock above that function a soft lock occurs when I disconnect. So I put it just below rtw_free_xmitframe_queue. Things works fine this way. Please tell me if there's a best way to do it. > > Regards, > > Hans thank you, fabio