public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: alvalan9@foxmail.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.15.y] wifi: ath10k: avoid NULL pointer error during sdio remove
Date: Tue, 18 Mar 2025 11:12:40 -0400	[thread overview]
Message-ID: <20250318080925-32aa4e1bb5cc535a@stable.kernel.org> (raw)
In-Reply-To: <tencent_891A70685F6B183EE224B3AC4F70FC60DC09@qq.com>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 95c38953cb1ecf40399a676a1f85dfe2b5780a9a

WARNING: Author mismatch between patch and upstream commit:
Backport author: alvalan9@foxmail.com
Commit author: Kang Yang<quic_kangyang@quicinc.com>

Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 543c0924d446)
6.6.y | Present (different SHA1: b35de9e01fc7)
6.1.y | Present (different SHA1: 6e5dbd1c04ab)

Note: The patch differs from the upstream commit:
---
1:  95c38953cb1ec ! 1:  4bc5b99f1591d wifi: ath10k: avoid NULL pointer error during sdio remove
    @@ Metadata
      ## Commit message ##
         wifi: ath10k: avoid NULL pointer error during sdio remove
     
    +    [ Upstream commit 95c38953cb1ecf40399a676a1f85dfe2b5780a9a ]
    +
         When running 'rmmod ath10k', ath10k_sdio_remove() will free sdio
         workqueue by destroy_workqueue(). But if CONFIG_INIT_ON_FREE_DEFAULT_ON
         is set to yes, kernel panic will happen:
    @@ Commit message
         Reviewed-by: David Ruth <druth@chromium.org>
         Link: https://patch.msgid.link/20241008022246.1010-1-quic_kangyang@quicinc.com
         Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
    +    Signed-off-by: Alva Lan <alvalan9@foxmail.com>
     
      ## drivers/net/wireless/ath/ath10k/sdio.c ##
     @@
       * Copyright (c) 2004-2011 Atheros Communications Inc.
       * Copyright (c) 2011-2012,2017 Qualcomm Atheros, Inc.
       * Copyright (c) 2016-2017 Erik Stromdahl <erik.stromdahl@gmail.com>
    -- * Copyright (c) 2022-2023 Qualcomm Innovation Center, Inc. All rights reserved.
     + * Copyright (c) 2022-2024 Qualcomm Innovation Center, Inc. All rights reserved.
       */
      
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y       |  Success    |  Success   |

      reply	other threads:[~2025-03-18 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18  7:32 [PATCH 5.15.y] wifi: ath10k: avoid NULL pointer error during sdio remove alvalan9
2025-03-18 15:12 ` Sasha Levin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250318080925-32aa4e1bb5cc535a@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=alvalan9@foxmail.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox