From: "Abhishek Sagar" <sagar.abhishek@gmail.com>
To: ananth@in.ibm.com
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>,
"Anil S Keshavamurthy" <anil.s.keshavamurthy@intel.com>,
"David Miller" <davem@davemloft.net>,
"Mathieu Desnoyers" <mathieu.desnoyers@polymtl.ca>,
hskinnemoen@atmel.com, "Masami Hiramatsu" <mhiramat@redhat.com>,
sam@ravnborg.org, randy.dunlap@oracle.com
Subject: Re: [PATCH 2/2] Kprobes: Move kprobes examples to samples/
Date: Tue, 5 Feb 2008 11:06:22 +0530 [thread overview]
Message-ID: <863e9df20802042136v5dbef855k5887e0c9cf9337d8@mail.gmail.com> (raw)
In-Reply-To: <20080205051256.GB12223@in.ibm.com>
On 2/5/08, Ananth N Mavinakayanahalli <ananth@in.ibm.com> wrote:
> + * Build and insert the kernel module as done in the kprobe example.
> + * You will see the trace data in /var/log/messages and on the console
> + * whenever sys_open() returns a negative value.
A passing observation...."sys_open" should be replaced with "do_fork",
whose return value is not checked at all.
--
Regards,
Abhishek
next prev parent reply other threads:[~2008-02-05 5:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 5:10 [PATCH 1/2] Kprobes: Indicate kretprobe support in Kconfig Ananth N Mavinakayanahalli
2008-02-05 5:12 ` [PATCH 2/2] Kprobes: Move kprobes examples to samples/ Ananth N Mavinakayanahalli
2008-02-05 5:36 ` Abhishek Sagar [this message]
2008-02-05 5:52 ` [PATCH 2/2] Kprobes: Move kprobes examples to samples/ - updated Ananth N Mavinakayanahalli
-- strict thread matches above, loose matches on Subject: below --
2008-01-03 6:24 [PATCH 1/2] Kprobes: Indicate kretprobe support in Kconfig Ananth N Mavinakayanahalli
2008-01-03 6:28 ` [PATCH 2/2] Kprobes: Move kprobes examples to samples/ Ananth N Mavinakayanahalli
2008-01-03 9:33 ` Ingo Molnar
2008-01-03 10:22 ` Ananth N Mavinakayanahalli
2008-01-03 11:04 ` Ingo Molnar
2008-01-03 15:18 ` Mathieu Desnoyers
2008-01-03 15:44 ` Ananth N Mavinakayanahalli
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=863e9df20802042136v5dbef855k5887e0c9cf9337d8@mail.gmail.com \
--to=sagar.abhishek@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®