From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Hugh Dickins <hugh@veritas.com>,
penberg@cs.helsinki.fi, rjw@sisk.pl, miles.lane@gmail.com,
linux-kernel@vger.kernel.org, cl@linux-foundation.org,
mingo@elte.hu, htejun@gmail.com, vegard.nossum@gmail.com,
rostedt@goodmis.org, arjan@infradead.org
Subject: Re: 2.6.28-rc6-git1 -- BUG: unable to handle kernel paging request at ffff8800be8b0019
Date: Tue, 2 Dec 2008 11:27:02 +1030 [thread overview]
Message-ID: <200812021127.03631.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20081201125103.db4c026f.akpm@linux-foundation.org>
On Tuesday 02 December 2008 07:21:03 Andrew Morton wrote:
> The fault really lies with include/linux/kallsyms.h, I think:
>
> #define KSYM_SYMBOL_LEN (sizeof("%s+%#lx/%#lx [%s]") + (KSYM_NAME_LEN - 1)
> + \ 2*(BITS_PER_LONG*3/10) + (MODULE_NAME_LEN - 1) + 1)
Hmm... and I recently define MODULE_NAME_LEN in terms of MAX_PARAM_PREFIX_LEN
for similar reasons.
Perhaps we should move MODULE_NAME_LEN to kernel.h and define everything in
terms of that? It seems to be a common need.
Rusty.
next prev parent reply other threads:[~2008-12-02 0:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 16:50 2.6.28-rc6-git1 -- BUG: unable to handle kernel paging request at ffff8800be8b0019 Miles Lane
2008-11-26 23:26 ` Rafael J. Wysocki
2008-11-27 13:37 ` Pekka Enberg
2008-11-27 13:50 ` Vegard Nossum
2008-11-27 13:54 ` Hugh Dickins
2008-11-27 14:13 ` Pekka Enberg
2008-11-27 17:34 ` Hugh Dickins
2008-11-27 21:23 ` Pekka Enberg
2008-11-27 21:56 ` Hugh Dickins
2008-11-27 22:51 ` Christoph Lameter
2008-11-28 7:57 ` Pekka Enberg
2008-11-27 23:27 ` Steven Rostedt
2008-11-27 23:31 ` Steven Rostedt
2008-11-28 0:16 ` Frederic Weisbecker
2008-11-29 6:40 ` Andrew Morton
2008-11-28 7:56 ` Pekka Enberg
2008-12-01 20:51 ` Andrew Morton
2008-12-01 22:47 ` Hugh Dickins
2008-12-02 0:57 ` Rusty Russell [this message]
2008-11-27 16:14 ` Miles Lane
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=200812021127.03631.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=cl@linux-foundation.org \
--cc=htejun@gmail.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--cc=rostedt@goodmis.org \
--cc=vegard.nossum@gmail.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