From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 206525] BUG: KASAN: stack-out-of-bounds in test_bit+0x30/0x44 (kernel 5.6-rc1)
Date: Thu, 20 Feb 2020 12:19:51 +0000 [thread overview]
Message-ID: <bug-206525-206035-1pA2iMCn9I@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206525-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206525
--- Comment #6 from Nikolay Aleksandrov (nikolay@cumulusnetworks.com) ---
Note that the bug wasn't introduced by my commit, but instead has been there
since:
commit 4f520900522f
Author: Richard Guy Briggs <rgb@redhat.com>
Date: Tue Apr 22 21:31:54 2014 -0400
netlink: have netlink per-protocol bind function return an error code.
which moved the ngroups test_bit() to a local variable. My commit only exposed
the bug since it added the 33rd group. I'm currently preparing a fix and will
post it to netdev after verifying and testing it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-02-20 12:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 20:07 [Bug 206525] New: BUG: KASAN: stack-out-of-bounds in test_bit+0x30/0x44 (kernel 5.6-rc1) bugzilla-daemon
2020-02-13 20:12 ` [Bug 206525] " bugzilla-daemon
2020-02-14 10:04 ` bugzilla-daemon
2020-02-15 17:52 ` bugzilla-daemon
2020-02-15 17:58 ` [netlink_bind()] " Christophe Leroy
2020-02-15 23:42 ` Nikolay Aleksandrov
2020-02-16 8:26 ` bugzilla-daemon
2020-02-17 10:53 ` bugzilla-daemon
2020-02-17 11:52 ` bugzilla-daemon
2020-02-20 12:19 ` bugzilla-daemon [this message]
2020-02-26 21:44 ` bugzilla-daemon
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-206525-206035-1pA2iMCn9I@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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.