Received-SPF: softfail (google.com: domain of transitioning linux-bluetooth-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: use hdev lock in activate_scan for
 hci_is_adv_monitoring
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <165061981237.24106.5638198039269621064.git-patchwork-notify@kernel.org>
Date:   Fri, 22 Apr 2022 09:30:12 +0000
References: <20220407180651.14871-1-dossche.niels@gmail.com>
In-Reply-To: <20220407180651.14871-1-dossche.niels@gmail.com>
To:     Niels Dossche <dossche.niels@gmail.com>
Cc:     linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
        johan.hedberg@gmail.com, luiz.dentz@gmail.com,
        howardchung@chromium.org
Precedence: bulk

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:

On Thu,  7 Apr 2022 20:06:52 +0200 you wrote:
> hci_is_adv_monitoring's function documentation states that it must be
> called under the hdev lock. Paths that leads to an unlocked call are:
> discov_update => start_discovery => interleaved_discov => active_scan
> and: discov_update => start_discovery => active_scan
> 
> The solution is to take the lock in active_scan during the duration of
> the call to hci_is_adv_monitoring.
> 
> [...]

Here is the summary with links:
  - Bluetooth: use hdev lock in activate_scan for hci_is_adv_monitoring
    https://git.kernel.org/bluetooth/bluetooth-next/c/e05c3c0e1b45

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html