From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 216389] net/bluetooth/l2cap_core.c fails bounds check with GCC 12.2
Date: Wed, 24 Aug 2022 12:36:25 +0000 [thread overview]
Message-ID: <bug-216389-62941-y9J6WOuzpW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216389-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216389
--- Comment #4 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Luiz Von Dentz from comment #3)
> The following patch should fix it:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/
> commit/?id=1d71d9223e4143d3638f60c7bb291844c237556c
Correct. Thanks!
I'll close here as 'fixed' when the patch makes it into -rc.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2022-08-24 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 11:50 [Bug 216389] New: net/bluetooth/l2cap_core.c fails bounds check with GCC 12.2 bugzilla-daemon
2022-08-22 2:01 ` [Bug 216389] " bugzilla-daemon
2022-08-23 10:45 ` bugzilla-daemon
2022-08-23 17:22 ` bugzilla-daemon
2022-08-24 12:36 ` bugzilla-daemon [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=bug-216389-62941-y9J6WOuzpW@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox