From: Avi Kivity <avi@argo.co.il>
To: Daniel Bonekeeper <thehazard@gmail.com>
Cc: Andreas Gruenbacher <agruen@suse.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: NULL terminate over-long /proc/kallsyms symbols
Date: Thu, 06 Jul 2006 21:00:01 +0300 [thread overview]
Message-ID: <44AD4FA1.2060200@argo.co.il> (raw)
In-Reply-To: <e1e1d5f40607051003v6b644e82p346c6e0661f39274@mail.gmail.com>
Daniel Bonekeeper wrote:
>
> Got a " You are not authorized to access bug #190296. To see this bug,
> you must first log in to an account with the appropriate permissions."
> on the referred bugzilla page.
>
> What kind of symbol uses more than 127 characters, anyways ?
>
Maybe C++ mangled names.
I've seen names longer than early machines' main memory.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2006-07-06 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 16:59 NULL terminate over-long /proc/kallsyms symbols Andreas Gruenbacher
2006-07-05 17:03 ` Daniel Bonekeeper
2006-07-05 17:06 ` Christoph Hellwig
2006-07-06 18:00 ` Avi Kivity [this message]
2006-07-05 17:13 ` Andreas Schwab
2006-07-05 19:34 ` Andrew Morton
2006-07-05 19:42 ` Andreas Gruenbacher
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=44AD4FA1.2060200@argo.co.il \
--to=avi@argo.co.il \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thehazard@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.