[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d31bc2e2718247a7b1db38593564262e@AcuMS.aculab.com>
Date: Fri, 21 Feb 2020 15:41:35 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Will Deacon' <will@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "kernel-team@...roid.com" <kernel-team@...roid.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"K . Prasad" <prasad@...ux.vnet.ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>,
Frederic Weisbecker <frederic@...nel.org>,
Christoph Hellwig <hch@....de>,
Quentin Perret <qperret@...gle.com>,
Alexei Starovoitov <ast@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>
Subject: RE: [PATCH 0/3] Unexport kallsyms_lookup_name() and
kallsyms_on_each_symbol()
From: Will Deacon
> Sent: 21 February 2020 11:44
> Hi folks,
>
> Despite having just a single modular in-tree user that I could spot,
> kallsyms_lookup_name() is exported to modules and provides a mechanism
> for out-of-tree modules to access and invoke arbitrary, non-exported
> kernel symbols when kallsyms is enabled.
Now where did I put that kernel code that opens /proc/kallsyms and
then reads it to find the addresses of symbols ...
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists