You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Possible use of unitialized socked address #132075
New Bluetooth tests added in #132023 fail on Fedora based platforms. It looks that the hci_channel member of the sockaddr_hci structure is not initialized. This may be a cause of the failure.
On NetBSD and DragonFly sockaddr_hci is an alias of sockaddr_bt which contain other fields. This also may be an issue.
If sockaddr_hci contains additional optional members, not initializing them with zeros also may cause troubles.
It is safer to always initialize sockaddr_hci and all other sockaddr_* structures with zeroes.
Activity
pythongh-132075: Fix possible use of sockaddr structures with uniniti…
gh-132075: Fix possible use of sockaddr structures with uninitialized…
pythongh-132075: Fix possible use of sockaddr structures with uniniti…
pythongh-132075: Fix possible use of sockaddr structures with uniniti…
[3.12] gh-132075: Fix possible use of sockaddr structures with uninit…
[3.13] gh-132075: Fix possible use of sockaddr structures with uninit…