Re: [PATCH] kprobes: Use module_name() macro

2020-08-19 Thread Jarkko Sakkinen
On Tue, Aug 18, 2020 at 01:00:45PM -0400, Steven Rostedt wrote: > On Tue, 18 Aug 2020 19:33:56 +0300 > Jarkko Sakkinen wrote: > > > > Acked-by: Masami Hiramatsu > > > > Great, thank you. > > > > When this might get included to a PR, or at minimum land to linux-next? > > > > Just thinking

Re: [PATCH] kprobes: Use module_name() macro

2020-08-18 Thread Steven Rostedt
On Tue, 18 Aug 2020 19:33:56 +0300 Jarkko Sakkinen wrote: > > Acked-by: Masami Hiramatsu > > Great, thank you. > > When this might get included to a PR, or at minimum land to linux-next? > > Just thinking what to use as the baseline for the next version of my > main series. I can apply

Re: [PATCH] kprobes: Use module_name() macro

2020-08-18 Thread Jarkko Sakkinen
On Tue, Aug 18, 2020 at 11:49:56PM +0900, Masami Hiramatsu wrote: > On Tue, 18 Aug 2020 08:08:57 +0300 > Jarkko Sakkinen wrote: > > > It is advised to use module_name() macro instead of dereferencing mod->name > > directly. This makes sense for consistencys sake and also it prevents a > > hard

Re: [PATCH] kprobes: Use module_name() macro

2020-08-18 Thread Masami Hiramatsu
On Tue, 18 Aug 2020 08:08:57 +0300 Jarkko Sakkinen wrote: > It is advised to use module_name() macro instead of dereferencing mod->name > directly. This makes sense for consistencys sake and also it prevents a > hard dependency to CONFIG_MODULES. > > Cc: linux...@kvack.org > Cc: Andi Kleen >

[PATCH] kprobes: Use module_name() macro

2020-08-17 Thread Jarkko Sakkinen
It is advised to use module_name() macro instead of dereferencing mod->name directly. This makes sense for consistencys sake and also it prevents a hard dependency to CONFIG_MODULES. Cc: linux...@kvack.org Cc: Andi Kleen Cc: Ard Biesheuvel Cc: Jessica Yu Cc: Mark Rutland , Cc: Masami Hiramatsu