[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200221142035.GA17979@willie-the-truck>
Date: Fri, 21 Feb 2020 14:20:35 +0000
From: Will Deacon <will@...nel.org>
To: Christoph Hellwig <hch@....de>
Cc: linux-kernel@...r.kernel.org, kernel-team@...roid.com,
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>,
Quentin Perret <qperret@...gle.com>,
Alexei Starovoitov <ast@...nel.org>,
Masami Hiramatsu <mhiramat@...nel.org>
Subject: Re: [PATCH 2/3] samples/hw_breakpoint: Drop use of
kallsyms_lookup_name()
On Fri, Feb 21, 2020 at 03:13:54PM +0100, Christoph Hellwig wrote:
> On Fri, Feb 21, 2020 at 11:44:03AM +0000, Will Deacon wrote:
> > -static char ksym_name[KSYM_NAME_LEN] = "pid_max";
> > +static char ksym_name[KSYM_NAME_LEN] = "jiffies";
>
> Is jiffies actually an exported symbol on all configfs? I thought
> there was some weird aliasing going on with jiffies64.
There is some weird aliasing with jiffies_64, but kernel/time/jiffies.c
has an unconditional:
EXPORT_SYMBOL(jiffies);
so I think we're ok.
> Except for the symbol choice this looks fine, though:
>
> Reviewed-by: Christoph Hellwig <hch@....de>
Brill, cheers.
Will
Powered by blists - more mailing lists