From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/21726] on rawhide, the backtrace.exp test case causes a kernel panic
Date: Fri, 14 Jul 2017 14:15:00 -0000 [thread overview]
Message-ID: <bug-21726-6586-szCq8itZKf@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-21726-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21726
--- Comment #5 from David Smith <dsmith at redhat dot com> ---
Commit 109e4e7 adds a workaround that avoids the kernel panic (by not calling
access_ok() in hard IRQ context).
For a longer term fix, we should remove uses of access_ok() in favor of our
uderef() / kderef() macros. There are other access_ok() uses in
runtime/linux/addr-map.c and tapset/linux/nfs.stp. These should all be replaced
if possible.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2017-07-14 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 15:26 [Bug runtime/21726] New: " dsmith at redhat dot com
2017-07-06 20:22 ` [Bug runtime/21726] " mark at klomp dot org
2017-07-06 20:31 ` mark at klomp dot org
2017-07-07 15:28 ` mark at klomp dot org
2017-07-07 15:36 ` mark at klomp dot org
2017-07-14 14:15 ` dsmith at redhat dot com [this message]
2017-07-20 14:49 ` dsmith at redhat dot com
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-21726-6586-szCq8itZKf@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).