From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 204479] KASAN hit at modprobe zram
Date: Thu, 08 Aug 2019 21:57:55 +0000 [thread overview]
Message-ID: <bug-204479-206035-1qc1NAmGNE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204479-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204479
--- Comment #6 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Christophe Leroy from comment #4)
> We need to identify if the allocation of KASAN shadow area at module
> allocation fails, or if kasan accesses outside of the allocated area.
>
> Could you please run again with the below trace:
The patch did not apply to the mainstream kernnel with 'patch -p1 < ...' but I
inserted the code manually. Please find the new results attached.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-08 22:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204479-206035@https.bugzilla.kernel.org/>
2019-08-05 0:34 ` [Bug 204479] KASAN hit at modprobe zram bugzilla-daemon
2019-08-05 7:07 ` bugzilla-daemon
2019-08-05 14:00 ` bugzilla-daemon
2019-08-08 13:57 ` bugzilla-daemon
2019-08-08 21:55 ` bugzilla-daemon
2019-08-08 21:57 ` bugzilla-daemon [this message]
2019-08-08 21:58 ` bugzilla-daemon
2019-08-09 5:34 ` bugzilla-daemon
2019-08-09 5:38 ` bugzilla-daemon
2019-08-09 10:44 ` bugzilla-daemon
2019-08-09 14:08 ` bugzilla-daemon
2019-08-09 15:10 ` bugzilla-daemon
2019-08-09 17:50 ` bugzilla-daemon
2019-08-09 17:52 ` bugzilla-daemon
2019-08-09 20:31 ` bugzilla-daemon
2019-08-10 14:42 ` bugzilla-daemon
2019-08-12 16:01 ` bugzilla-daemon
2019-08-12 16:06 ` bugzilla-daemon
2019-08-13 11:12 ` bugzilla-daemon
2019-08-13 11:21 ` bugzilla-daemon
2019-08-13 11:49 ` bugzilla-daemon
2019-10-06 20:52 ` 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-204479-206035-1qc1NAmGNE@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.