public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Van Hensbergen <ericvh@hera.kernel.org>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org,
	v9fs-developer@lists.sourceforge.net, ericvh@gmail.com
Subject: [RESEND][PATCH] v9fs: print v9fs module address
Date: Fri, 17 Mar 2006 19:09:14 GMT	[thread overview]
Message-ID: <200603171909.k2HJ9BiD006068@hera.kernel.org> (raw)

Subject: [PATCH] print v9fs module address
From: Latchesar Ionkov <lucho@ionkov.net>
Date: 1141313037 -0500

This patch prints v9fs module address when the module is initialized. It is
useful to have it in the logs -- if the kernel crashes the address can be
used together with the oops print to find out the exact place (presumably in
the v9fs code) that cause the oops.

Signed-off-by: Latchesar Ionkov <lucho@ionkov.net>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>

---

 fs/9p/v9fs.c |    7 ++++++-
 1 files changed, 6 insertions(+), 1 deletions(-)

3e12299e1cd1582b67aa57ff9b445e9af61a4701
diff --git a/fs/9p/v9fs.c b/fs/9p/v9fs.c
index daf623c..321989a 100644
--- a/fs/9p/v9fs.c
+++ b/fs/9p/v9fs.c
@@ -455,10 +455,15 @@ extern int v9fs_error_init(void);
 static int __init init_v9fs(void)
 {
 	int ret;
+	void *mcore;
+
+	mcore = NULL;
+	if (THIS_MODULE)
+		mcore = THIS_MODULE->module_core;
 
 	v9fs_error_init();
 
-	printk(KERN_INFO "Installing v9fs 9P2000 file system support\n");
+	printk(KERN_INFO "Installing v9fs 9P2000 file system support %p\n", mcore);
 
 	ret = v9fs_mux_global_init();
 	if (!ret)
-- 
1.1.0

             reply	other threads:[~2006-03-17 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-17 19:09 Eric Van Hensbergen [this message]
2006-03-17 19:41 ` [RESEND][PATCH] v9fs: print v9fs module address Christoph Hellwig
2006-03-17 21:03   ` Andrew Morton
2006-03-18  1:59     ` [V9fs-developer] " Latchesar Ionkov

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=200603171909.k2HJ9BiD006068@hera.kernel.org \
    --to=ericvh@hera.kernel.org \
    --cc=akpm@osdl.org \
    --cc=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=v9fs-developer@lists.sourceforge.net \
    /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