Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem()
 failure
From:   patchwork-bot+bluetooth@kernel.org
Message-Id: <166360921484.3099.15829097107385180514.git-patchwork-notify@kernel.org>
Date:   Mon, 19 Sep 2022 17:40:14 +0000
References: <376d3dd4-725a-a212-2701-09a80b7d3915@I-love.SAKURA.ne.jp>
In-Reply-To: <376d3dd4-725a-a212-2701-09a80b7d3915@I-love.SAKURA.ne.jp>
To:     Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc:     marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com,
        ronald@innovation.ch, lukas@wunner.de,
        syzbot+576dfca25381fb6fbc5f@syzkaller.appspotmail.com,
        syzkaller-bugs@googlegroups.com, linux-bluetooth@vger.kernel.org
Precedence: bulk

Hello:

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

On Mon, 29 Aug 2022 23:58:12 +0900 you wrote:
> syzbot is reporting NULL pointer dereference at hci_uart_tty_close() [1],
> for rcu_sync_enter() is called without rcu_sync_init() due to
> hci_uart_tty_open() ignoring percpu_init_rwsem() failure.
> 
> While we are at it, fix that hci_uart_register_device() ignores
> percpu_init_rwsem() failure and hci_uart_unregister_device() does not
> call percpu_free_rwsem().
> 
> [...]

Here is the summary with links:
  - Bluetooth: hci_{ldisc,serdev}: check percpu_init_rwsem() failure
    https://git.kernel.org/bluetooth/bluetooth-next/c/3124d320c22f

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