From: Martin Hunt <hunt@redhat.com>
To: sourceware-bugzilla@sourceware.org
Cc: systemtap@sources.redhat.com
Subject: Re: [Bug kprobes/2637] skipped probes in FC6
Date: Thu, 11 May 2006 16:30:00 -0000 [thread overview]
Message-ID: <1147365024.2632.10.camel@dragon> (raw)
In-Reply-To: <20060505213345.1366.qmail@sourceware.org>
On Fri, 2006-05-05 at 21:33 +0000, anil dot s dot keshavamurth
> Hence the right thing to do here is to catch that page_fault exceptions and
> try fixing up the exceptions without falling back on do_page_fault() code path.
> With this simple fix, you would now experience any copy_from_user() calls from
> pre/post hanlder to fail if that page is not in memory.
I agree. I have been looking into this and could use some help.
next prev parent reply other threads:[~2006-05-11 16:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-02 20:13 [Bug kprobes/2637] New: " hunt at redhat dot com
2006-05-02 20:18 ` [Bug kprobes/2637] " hunt at redhat dot com
2006-05-02 20:25 ` hunt at redhat dot com
2006-05-03 13:05 ` prasanna at in dot ibm dot com
2006-05-03 13:08 ` fche at redhat dot com
2006-05-04 4:22 ` hunt at redhat dot com
2006-05-05 6:56 ` prasanna at in dot ibm dot com
2006-05-05 13:49 ` fche at redhat dot com
2006-05-05 16:45 ` Martin Hunt
2006-05-05 16:42 ` hunt at redhat dot com
2006-05-05 16:45 ` hunt at redhat dot com
2006-05-05 21:33 ` anil dot s dot keshavamurthy at intel dot com
2006-05-11 16:30 ` Martin Hunt [this message]
2006-05-11 16:30 ` hunt at redhat dot com
2006-05-11 17:01 ` anil dot s dot keshavamurthy at intel dot com
2006-05-15 6:52 ` prasanna at in dot ibm dot com
2006-05-31 21:58 ` [Bug runtime/2637] " jkenisto at us dot ibm 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=1147365024.2632.10.camel@dragon \
--to=hunt@redhat.com \
--cc=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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).