All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Zhengping Jiang <jiangzp@google.com>
Cc: linux-bluetooth@vger.kernel.org, marcel@holtmann.org,
	chromeos-bluetooth-upstreaming@chromium.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, johan.hedberg@gmail.com,
	luiz.dentz@gmail.com, pabeni@redhat.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [kernel PATCH v3 0/1] Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn
Date: Wed, 24 Aug 2022 22:30:17 +0000	[thread overview]
Message-ID: <166138021700.13438.5071641895623832276.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220823172808.3477638-1-jiangzp@google.com>

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Tue, 23 Aug 2022 10:28:07 -0700 you wrote:
> Hold hdev->lock for hci_conn_failed. There are possible race conditions
> which may cause kernel crash.
> 
> Changes in v3:
> - Remove an empty line in commit message between Fixes and SoB
> 
> Changes in v2:
> - Update commit message
> 
> [...]

Here is the summary with links:
  - [kernel,v3,1/1] Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn
    https://git.kernel.org/bluetooth/bluetooth-next/c/808765508e8e

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



      parent reply	other threads:[~2022-08-24 22:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 17:28 [kernel PATCH v3 0/1] Bluetooth: hci_sync: hold hdev->lock when cleanup hci_conn Zhengping Jiang
2022-08-23 17:28 ` [kernel PATCH v3 1/1] " Zhengping Jiang
2022-08-23 19:59   ` bluez.test.bot
2022-08-24 22:30 ` patchwork-bot+bluetooth [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=166138021700.13438.5071641895623832276.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=chromeos-bluetooth-upstreaming@chromium.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiangzp@google.com \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.