All of lore.kernel.org
 help / color / mirror / Atom feed
From: AliOS system security <alios_sys_security@linux.alibaba.com>
To: masahiroy@kernel.org, michal.lkml@markovi.net
Cc: linux-kbuild@vger.kernel.org,
	AliOS system security <alios_sys_security@linux.alibaba.com>
Subject: [PATCH] mksysmap: Fix the mismatch of '.L' symbols in System.map
Date: Sun, 31 May 2020 18:28:24 +0800	[thread overview]
Message-ID: <1590920904-60002-1-git-send-email-alios_sys_security@linux.alibaba.com> (raw)

When System.map was generated, the kernel used mksysmap to filter the
kernel symbols, but all the symbols with the second letter 'L' in the
kernel were filtered out, not just the symbols starting with 'dot + L'.

For example:
ashimida@ubuntu:~/linux$ cat System.map |grep ' .L'
ashimida@ubuntu:~/linux$ nm -n vmlinux |grep ' .L'
ffff0000088028e0 t bLength_show
......
ffff0000092e0408 b PLLP_OUTC_lock
ffff0000092e0410 b PLLP_OUTA_lock

I see that in the original patch[1], the original intent should be to
filter all local symbols starting with '.L', so I wonder if the code
here may add a '\' before '.L'?

[1]. mksysmap: Add h8300 local symbol pattern

Signed-off-by: AliOS system security <alios_sys_security@linux.alibaba.com>
---
 scripts/mksysmap | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/mksysmap b/scripts/mksysmap
index a35acc0..9aa23d1 100755
--- a/scripts/mksysmap
+++ b/scripts/mksysmap
@@ -41,4 +41,4 @@
 # so we just ignore them to let readprofile continue to work.
 # (At least sparc64 has __crc_ in the middle).
 
-$NM -n $1 | grep -v '\( [aNUw] \)\|\(__crc_\)\|\( \$[adt]\)\|\( .L\)' > $2
+$NM -n $1 | grep -v '\( [aNUw] \)\|\(__crc_\)\|\( \$[adt]\)\|\( \.L\)' > $2
-- 
2.7.4

             reply	other threads:[~2020-05-31 10:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-31 10:28 AliOS system security [this message]
2020-06-01 11:01 ` [PATCH] mksysmap: Fix the mismatch of '.L' symbols in System.map Masahiro Yamada
2020-06-02  6:41   ` AliOS system security
2020-06-02  1:50 ` Masahiro Yamada
2020-06-02  7:45 ` [PATCH v2] " ashimida
2020-06-02 14:42   ` Masahiro Yamada

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=1590920904-60002-1-git-send-email-alios_sys_security@linux.alibaba.com \
    --to=alios_sys_security@linux.alibaba.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.lkml@markovi.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 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.