[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALkUMdQanGgtahQDqQV-r6oWF=cvTsteztOoe5bqHsJApST0Rw@mail.gmail.com>
Date: Wed, 27 Apr 2022 18:01:34 +0530
From: Vimal Agrawal <avimalin@...il.com>
To: Luis Chamberlain <mcgrof@...nel.org>
Cc: Maninder Singh <maninder1.s@...sung.com>,
Petr Mladek <pmladek@...e.com>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"senozhatsky@...omium.org" <senozhatsky@...omium.org>,
"andriy.shevchenko@...ux.intel.com"
<andriy.shevchenko@...ux.intel.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"wangkefeng.wang@...wei.com" <wangkefeng.wang@...wei.com>,
"wedsonaf@...gle.com" <wedsonaf@...gle.com>,
"boqun.feng@...il.com" <boqun.feng@...il.com>,
"christophe.leroy@...roup.eu" <christophe.leroy@...roup.eu>,
"swboyd@...omium.org" <swboyd@...omium.org>,
"ojeda@...nel.org" <ojeda@...nel.org>,
"ast@...nel.org" <ast@...nel.org>,
"gary@...yguo.net" <gary@...yguo.net>,
"mbenes@...e.cz" <mbenes@...e.cz>,
"ndesaulniers@...gle.com" <ndesaulniers@...gle.com>,
"void@...ifault.com" <void@...ifault.com>,
"jolsa@...nel.org" <jolsa@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Vaneet Narang <v.narang@...sung.com>,
Onkarnath <onkarnath.1@...sung.com>
Subject: Re: [PATCH 1/1] kallsyms: add kallsyms_show_value definition in all cases
Hi Maninder,
in sprint_module_info(), we need to take care of mod->init_layout
addresses as well.
Please test the patch against init symbols.
Vimal
On Wed, Apr 20, 2022 at 8:51 PM Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> On Mon, Apr 18, 2022 at 10:04:42AM +0530, Maninder Singh wrote:
> > > What about splitting kallsyms.c into two source files where one
> > > would be always compiled? It would be usable also for the
> > > spring function introduced by
> > > https://lore.kernel.org/r/20220323164742.2984281-1-maninder1.s@samsung.com
> > >
> > > It might be something like kallsyms_full.c and/or kallsyms_tiny.c.
> > >
> >
> > This patch is not taken by Luis yet in module-tetsing branch.
>
> Please resend that patch, as I'm happy to route it in through
> modules-next [0]. I use modules-testing *prior* to pushing to
> modules-next, if 0-day does not complain after about a few days
> then I push to modules-next and this gets merged to linux-next.
>
> You can send that patch and then this one and include in the subject
> something like:
>
> [PATCH modules-next 1/1]
>
> Vimal, I'd like your review of these patches too. And after those
> we can see where your change fits / if it is still needed.
>
> [0] https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git/log/?h=modules-next
>
> Luis
Powered by blists - more mailing lists