From: Jakub Kicinski <kuba@kernel.org>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: davem@davemloft.net, linux-bluetooth@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: pull-request: bluetooth 2023-10-11
Date: Fri, 13 Oct 2023 17:54:43 -0700 [thread overview]
Message-ID: <20231013175443.5cb5c2ce@kernel.org> (raw)
In-Reply-To: <20231011191524.1042566-1-luiz.dentz@gmail.com>
On Wed, 11 Oct 2023 12:15:24 -0700 Luiz Augusto von Dentz wrote:
> - Fix race when opening vhci device
> - Avoid memcmp() out of bounds warning
> - Correctly bounds check and pad HCI_MON_NEW_INDEX name
> - Fix using memcmp when comparing keys
> - Ignore error return for hci_devcd_register() in btrtl
> - Always check if connection is alive before deleting
> - Fix a refcnt underflow problem for hci_conn
Commit: fc11ae648f03 ("Bluetooth: hci_sock: Correctly bounds check and pad HCI_MON_NEW_INDEX name")
Fixes tag: Fixes: 78480de55a96 ("Bluetooth: hci_sock: fix slab oob read in create_monitor_event")
Has these problem(s):
- Target SHA1 does not exist
Commit: 6f0ff718ed67 ("Bluetooth: avoid memcmp() out of bounds warning")
Fixes tag: Fixes: d70e44fef8621 ("Bluetooth: Reject connection with the device which has same BD_ADDR")
Has these problem(s):
- Target SHA1 does not exist
Commit: b03f32b195df ("Bluetooth: hci_event: Fix coding style")
Fixes tag: Fixes: d70e44fef862 ("Bluetooth: Reject connection with the device which has same BD_ADDR")
Has these problem(s):
- Target SHA1 does not exist
Commit: a9500f272b3b ("Bluetooth: hci_event: Fix using memcmp when comparing keys")
Fixes tag: Fixes: fe7a9da4fa54 ("Bluetooth: hci_event: Ignore NULL link key")
Has these problem(s):
- Target SHA1 does not exist
:(
next prev parent reply other threads:[~2023-10-14 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 19:15 pull-request: bluetooth 2023-10-11 Luiz Augusto von Dentz
2023-10-14 0:54 ` Jakub Kicinski [this message]
2023-10-14 3:12 ` Luiz Augusto von Dentz
2023-10-16 6:38 ` Paolo Abeni
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=20231013175443.5cb5c2ce@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=netdev@vger.kernel.org \
/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.