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 v2] Bluetooth: use hdev lock for accept_list and reject_list
 in conn req
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <165061981233.24106.17851581389197850076.git-patchwork-notify@kernel.org>
Date:   Fri, 22 Apr 2022 09:30:12 +0000
References: <20220405173751.7269-1-dossche.niels@gmail.com>
In-Reply-To: <20220405173751.7269-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
Precedence: bulk

Hello:

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

On Tue,  5 Apr 2022 19:37:52 +0200 you wrote:
> All accesses (both reads and modifications) to
> hdev->{accept,reject}_list are protected by hdev lock,
> except the ones in hci_conn_request_evt. This can cause a race
> condition in the form of a list corruption.
> The solution is to protect these lists in hci_conn_request_evt as well.
> 
> I was unable to find the exact commit that introduced the issue for the
> reject list, I was only able to find it for the accept list.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: use hdev lock for accept_list and reject_list in conn req
    https://git.kernel.org/bluetooth/bluetooth-next/c/1072b8391c7c

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