linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>
Subject: Letext symbols in System.map
Date: 17 Oct 2003 13:59:59 -0700	[thread overview]
Message-ID: <1066424399.2589.171.camel@nighthawk> (raw)

I've been seeing intermittent Letext symbols showing up in System.maps
for a while.  They're annoying because they seem to plant themselves at
the same address as spinlocks and readprofile picks them over the
spinlock symbol.  

c02c40d9 t .text.lock.af_packet
c02c40d9 t Letext

For me, they only show up when CONFIG_DEBUG_INFO is turned on, but
Martin Bligh claims he's seen them other times as well.  

After some googling, it appears that Letext is supposed to be a label
for a string constant.  Since the spinlocks are defined using assembly
inside string constants, perhaps the label for that asm string is
hanging around too long.  

Is ther anything to keep us from simply grepping them away when
System.map is created?  

$(NM) $@ | grep -v '\(compiled\)\|\(\.o$$\)\|\( [aUw] \)\|\(\.\.ng$$\)\|\(LASH[RL]DI\)\|\(Letext\)' | sort > System.map

-- 
Dave Hansen
haveblue@us.ibm.com


                 reply	other threads:[~2003-10-17 21:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1066424399.2589.171.camel@nighthawk \
    --to=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.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;
as well as URLs for NNTP newsgroup(s).