[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eff67256-ea61-ef88-251b-b67fcf6a9538@gmail.com>
Date: Sun, 18 Dec 2016 16:54:07 +0200
From: Nikolay Borisov <n.borisov.lkml@...il.com>
To: Jiri Slaby <jslaby@...e.cz>,
Arend Van Spriel <arend.vanspriel@...adcom.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Adam Borowski <kilobyte@...band.pl>,
Nicholas Piggin <npiggin@...il.com>,
Omar Sandoval <osandov@...ndov.com>,
Michal Marek <mmarek@...e.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Al Viro <viro@...iv.linux.org.uk>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>
Subject: Re: [GIT PULL] kbuild changes for v4.9-rc1
On 18.12.2016 16:45, Jiri Slaby wrote:
> Moreover, with some modules, __put_user_1 and others are reported
> instead of mcount.
nm vmlinux | grep __fentry__
nm vmlinux | grep mcount
What do these report ? I bet you that in your vmlinux the first one
would return something like :
ffffffff822f1810 T __fentry__
ffffffff827fdc20 r __kcrctab___fentry__
ffffffff82809461 r __kstrtab___fentry__
ffffffff827e6c20 R __ksymtab___fentry__
and nothing for the second. Whereas doing nm on the module in question
would give nothing for __fentry__ and something like: U mcount
Powered by blists - more mailing lists