From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 208181] BUG: KASAN: stack-out-of-bounds in strcmp+0x58/0xd8
Date: Thu, 02 Jul 2020 12:00:22 +0000 [thread overview]
Message-ID: <bug-208181-206035-0fb4dzJCkp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208181-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208181
--- Comment #11 from Christophe Leroy (christophe.leroy@csgroup.eu) ---
The issue is that that commit moved more code than described into kasan_init():
Kasan Pages allocation have to be moved into kasan_init() but page tables
allocation must remain before the switch to the final hash table.
Problem only occurs on book3s/32 having hash MMU.
See proposed fix at
https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=187165 (2
patches).
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-07-02 12:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 11:17 [Bug 208181] New: BUG: KASAN: stack-out-of-bounds in strcmp+0x58/0xd8 bugzilla-daemon
2020-06-15 11:22 ` [Bug 208181] " bugzilla-daemon
2020-06-29 14:31 ` bugzilla-daemon
2020-06-29 14:32 ` bugzilla-daemon
2020-06-29 14:42 ` bugzilla-daemon
2020-06-29 14:55 ` bugzilla-daemon
2020-06-29 16:57 ` bugzilla-daemon
2020-06-29 16:57 ` bugzilla-daemon
2020-06-30 12:29 ` bugzilla-daemon
2020-06-30 17:28 ` bugzilla-daemon
2020-07-02 8:47 ` bugzilla-daemon
2020-07-02 12:00 ` bugzilla-daemon [this message]
2020-07-02 17:18 ` bugzilla-daemon
2020-07-02 17:40 ` bugzilla-daemon
2020-07-03 1:12 ` bugzilla-daemon
2020-07-03 4:55 ` bugzilla-daemon
2020-07-14 22:35 ` bugzilla-daemon
2020-09-04 22:19 ` bugzilla-daemon
2020-09-04 22:21 ` bugzilla-daemon
2020-09-04 22:57 ` 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-208181-206035-0fb4dzJCkp@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.