From: Greg KH <greg@kroah.com>
To: Luca Falavigna <dktrkranz@gmail.com>
Cc: vamsi_krishna@in.ibm.com, prasanna@in.ibm.com,
Nathan Lynch <nathanl@austin.ibm.com>,
suparna@in.ibm.com, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Kprobes /proc entry
Date: Thu, 13 Jan 2005 15:34:46 -0800 [thread overview]
Message-ID: <20050113233446.GA2710@kroah.com> (raw)
In-Reply-To: <41E70234.50900@gmail.com>
On Fri, Jan 14, 2005 at 12:20:20AM +0100, Luca Falavigna wrote:
>
> +#ifdef CONFIG_DEBUG_FS
This ifdef should not be needed.
> +int kprobes_open(struct inode *inode, struct file *file)
Shouldn't these calls be static?
> +{
> + try_module_get(THIS_MODULE);
Check the return value of this call?
> static int __init init_kprobes(void)
> {
> int i, err = 0;
> @@ -140,6 +233,16 @@
> for (i = 0; i < KPROBE_TABLE_SIZE; i++)
> INIT_HLIST_HEAD(&kprobe_table[i]);
>
> +#ifdef CONFIG_DEBUG_FS
ifdef not needed.
> + if(!(kprobes_dir = debugfs_create_dir("kprobes", NULL)))
> + return -ENODEV;
> + if(!(kprobes_list = debugfs_create_file("list", S_IRUGO, kprobes_dir,
> + NULL, &kprobes_fops))) {
> + debugfs_remove(kprobes_dir);
> + return -ENODEV;
> + }
You never delete this file or directory on module unload, do you?
thanks,
greg k-h
next prev parent reply other threads:[~2005-01-13 23:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 16:25 [PATCH] Kprobes /proc entry Luca Falavigna
2005-01-10 18:14 ` Greg KH
2005-01-11 21:31 ` Nathan Lynch
2005-01-11 21:34 ` Greg KH
2005-01-12 0:09 ` Luca Falavigna
2005-01-12 6:35 ` Prasanna S Panchamukhi
2005-01-12 9:49 ` Prasanna S Panchamukhi
2005-01-13 23:20 ` Luca Falavigna
2005-01-13 23:34 ` Greg KH [this message]
2005-01-17 16:58 ` Luca Falavigna
2005-01-18 6:44 ` Greg KH
2005-01-20 14:13 ` Luca Falavigna
2005-01-14 0:22 ` Stephen Hemminger
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=20050113233446.GA2710@kroah.com \
--to=greg@kroah.com \
--cc=dktrkranz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathanl@austin.ibm.com \
--cc=prasanna@in.ibm.com \
--cc=suparna@in.ibm.com \
--cc=vamsi_krishna@in.ibm.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