From: Masahiro Yamada <masahiroy@kernel.org>
To: AliOS system security <alios_sys_security@linux.alibaba.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH] mksysmap: Fix the mismatch of '.L' symbols in System.map
Date: Tue, 2 Jun 2020 10:50:36 +0900 [thread overview]
Message-ID: <CAK7LNATDKUbtJPNuFtbBTd2sg3=Fn_E_fq_9VP0oK1BT7mo0KA@mail.gmail.com> (raw)
In-Reply-To: <1590920904-60002-1-git-send-email-alios_sys_security@linux.alibaba.com>
On Sun, May 31, 2020 at 7:28 PM AliOS system security
<alios_sys_security@linux.alibaba.com> wrote:
>
> 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>
I think you should submit this patch
with your real name instead of
the team name.
--
Best Regards
Masahiro Yamada
next prev parent reply other threads:[~2020-06-02 1:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 10:28 [PATCH] mksysmap: Fix the mismatch of '.L' symbols in System.map AliOS system security
2020-06-01 11:01 ` Masahiro Yamada
2020-06-02 6:41 ` AliOS system security
2020-06-02 1:50 ` Masahiro Yamada [this message]
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='CAK7LNATDKUbtJPNuFtbBTd2sg3=Fn_E_fq_9VP0oK1BT7mo0KA@mail.gmail.com' \
--to=masahiroy@kernel.org \
--cc=alios_sys_security@linux.alibaba.com \
--cc=linux-kbuild@vger.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.