From: Christoph Hellwig <hch@infradead.org>
To: Eric Van Hensbergen <ericvh@hera.kernel.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net, ericvh@gmail.com
Subject: Re: [RESEND][PATCH] v9fs: print v9fs module address
Date: Fri, 17 Mar 2006 19:41:13 +0000 [thread overview]
Message-ID: <20060317194113.GA8848@infradead.org> (raw)
In-Reply-To: <200603171909.k2HJ9BiD006068@hera.kernel.org>
On Fri, Mar 17, 2006 at 07:09:14PM +0000, Eric Van Hensbergen wrote:
> 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.
NACK.
This just clutters the log. The information is provided in /proc/modules
for all modules.
next prev parent reply other threads:[~2006-03-17 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-17 19:09 [RESEND][PATCH] v9fs: print v9fs module address Eric Van Hensbergen
2006-03-17 19:41 ` Christoph Hellwig [this message]
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=20060317194113.GA8848@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=ericvh@gmail.com \
--cc=ericvh@hera.kernel.org \
--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