Re: [PATCH] init, fix initcall blacklist for modules

2016-06-14 Thread Andrew Morton
On Tue, 14 Jun 2016 05:59:46 -0400 Prarit Bhargava wrote: > On 06/13/2016 04:59 PM, Rasmus Villemoes wrote: > > On Mon, Jun 13 2016, Prarit Bhargava wrote: > > > >> Sorry ... forgot to cc everyone on the last email. > >> > >> P. > >> > >> 8< > >> > >> sprint_symbol_no_offset() returns t

Re: [PATCH] init, fix initcall blacklist for modules

2016-06-14 Thread Prarit Bhargava
On 06/13/2016 04:59 PM, Rasmus Villemoes wrote: > On Mon, Jun 13 2016, Prarit Bhargava wrote: > >> Sorry ... forgot to cc everyone on the last email. >> >> P. >> >> 8< >> >> sprint_symbol_no_offset() returns the string "function_name [module_name]" >> where [module_name] is not printed

Re: [PATCH] init, fix initcall blacklist for modules

2016-06-13 Thread Rasmus Villemoes
On Mon, Jun 13 2016, Prarit Bhargava wrote: > Sorry ... forgot to cc everyone on the last email. > > P. > > 8< > > sprint_symbol_no_offset() returns the string "function_name [module_name]" > where [module_name] is not printed for built in kernel functions. This > means that the initcall

[PATCH] init, fix initcall blacklist for modules

2016-06-13 Thread Prarit Bhargava
Sorry ... forgot to cc everyone on the last email. P. 8< sprint_symbol_no_offset() returns the string "function_name [module_name]" where [module_name] is not printed for built in kernel functions. This means that the initcall blacklisting code will now always fail when comparing module

[PATCH] init, fix initcall blacklist for modules

2016-06-13 Thread Prarit Bhargava
sprint_symbol_no_offset() returns the string "function_name [module_name]" where [module_name] is not printed for built in kernel functions. This means that the initcall blacklisting code will now always fail when comparing module_init() function names. This patch resolves the issue by comparing