From: patchwork-bot+bluetooth@kernel.org
To: Pavel Skripkin <paskripkin@gmail.com>
Cc: marcel@holtmann.org, johan.hedberg@gmail.com,
luiz.dentz@gmail.com, hildawu@realtek.com, apusaka@chromium.org,
linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+b9bd12fbed3485a3e51f@syzkaller.appspotmail.com
Subject: Re: [PATCH] Bluetooth: hci_uart: add missing NULL check in h5_enqueue
Date: Mon, 14 Mar 2022 15:40:10 +0000 [thread overview]
Message-ID: <164727241064.27748.11693637138240755601.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220313174936.1299-1-paskripkin@gmail.com>
Hello:
This patch was applied to bluetooth/bluetooth-next.git (master)
by Marcel Holtmann <marcel@holtmann.org>:
On Sun, 13 Mar 2022 20:49:36 +0300 you wrote:
> Syzbot hit general protection fault in __pm_runtime_resume(). The problem
> was in missing NULL check.
>
> hu->serdev can be NULL and we should not blindly pass &serdev->dev
> somewhere, since it will cause GPF.
>
> Reported-by: syzbot+b9bd12fbed3485a3e51f@syzkaller.appspotmail.com
> Fixes: d9dd833cf6d2 ("Bluetooth: hci_h5: Add runtime suspend")
> Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
>
> [...]
Here is the summary with links:
- Bluetooth: hci_uart: add missing NULL check in h5_enqueue
https://git.kernel.org/bluetooth/bluetooth-next/c/928df045e94e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-03-14 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 17:49 Pavel Skripkin
2022-03-14 15:34 ` Marcel Holtmann
2022-03-14 15:40 ` 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=164727241064.27748.11693637138240755601.git-patchwork-notify@kernel.org \
--to=patchwork-bot+bluetooth@kernel.org \
--cc=apusaka@chromium.org \
--cc=hildawu@realtek.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=marcel@holtmann.org \
--cc=paskripkin@gmail.com \
--cc=syzbot+b9bd12fbed3485a3e51f@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®