From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 204819] KASAN still got problems loading some modules at boot
Date: Mon, 16 Sep 2019 13:39:53 +0000 [thread overview]
Message-ID: <bug-204819-206035-kZuZwRCjVq@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204819-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204819
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #25 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Christophe Leroy from comment #24)
> Do you confirm that the two patches done in the scope of bug #204479 are
> included in your config, especially the first one:
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
> arch/powerpc/mm/kasan/kasan_init_32.
> c?id=663c0c9496a69f80011205ba3194049bcafd681d
> https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/
> arch/powerpc/mm/kasan/kasan_init_32.
> c?id=45ff3c55958542c3b76075d59741297b8cb31cbb
Ahh, now we are getting closer...
No, I did the testing with a vanilla 5.3-rc8 kernel assuming that
powerpc/kasan: Fix shadow area set up for modules
powerpc/kasan: Fix parallel loading of modules
were already in 5.3-rc8. Now I realize I was wrong.
In -rc8 the latest one (2019-07-31) is:
powerpc/kasan: fix early boot failure on PPC32
The other two patches are dated 2019-08-20 and not in 5.3-rc8 or the newly
released 5.3.
Sorry for the noise! I will close the bug for now and retest as soon as the 2
patches are in 5.4-rcx or 5.3.x. If it still seems valid that time I will
re-open.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-09-16 13:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 22:47 [Bug 204819] New: KASAN still got problems loading some modules at boot bugzilla-daemon
2019-09-11 22:48 ` [Bug 204819] " bugzilla-daemon
2019-09-12 5:09 ` bugzilla-daemon
2019-09-13 15:51 ` bugzilla-daemon
2019-09-13 15:52 ` bugzilla-daemon
2019-09-13 15:52 ` bugzilla-daemon
2019-09-14 8:15 ` bugzilla-daemon
2019-09-14 8:21 ` bugzilla-daemon
2019-09-14 8:26 ` bugzilla-daemon
2019-09-14 14:19 ` bugzilla-daemon
2019-09-14 16:47 ` bugzilla-daemon
2019-09-16 5:50 ` bugzilla-daemon
2019-09-16 11:10 ` bugzilla-daemon
2019-09-16 11:11 ` bugzilla-daemon
2019-09-16 11:12 ` bugzilla-daemon
2019-09-16 11:13 ` bugzilla-daemon
2019-09-16 11:13 ` bugzilla-daemon
2019-09-16 11:14 ` bugzilla-daemon
2019-09-16 11:15 ` bugzilla-daemon
2019-09-16 11:16 ` bugzilla-daemon
2019-09-16 11:16 ` bugzilla-daemon
2019-09-16 11:16 ` bugzilla-daemon
2019-09-16 11:20 ` bugzilla-daemon
2019-09-16 11:32 ` bugzilla-daemon
2019-09-16 12:28 ` bugzilla-daemon
2019-09-16 13:39 ` bugzilla-daemon [this message]
2019-09-18 5:54 ` 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-204819-206035-kZuZwRCjVq@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).