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 11:32:23 +0000 [thread overview]
Message-ID: <bug-204819-206035-a1juqETDTk@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204819-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204819
--- Comment #23 from Christophe Leroy (christophe.leroy@c-s.fr) ---
Thanks. The third one is interesting, as it shows :
Sep 16 12:57:39 T600 kernel: BUG: Unable to handle kernel data access at
0xfe295404
0xfe295000-0xfe295fff 0x00d05000 4K user r present
accessed
So unlike the other cases, this one shows that the area is still read-only and
pointing to the zero shadow area.
Wondering whether for the other ones the area is not allocated to a further
module loader after the failing one.
Are you able to dump kernel_page_tables just after each module load failure
before loading any additional module ?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-09-16 11:42 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 [this message]
2019-09-16 12:28 ` bugzilla-daemon
2019-09-16 13:39 ` bugzilla-daemon
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-a1juqETDTk@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.