public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Yang Shi <yang.shi@linaro.org>, Ingo Molnar <mingo@kernel.org>,
	Mel Gorman <mgorman@suse.de>, Kees Cook <keescook@chromium.org>,
	Yaowei Bai <baiyaowei@cmss.chinamobile.com>,
	Andrey Ryabinin <aryabinin@virtuozzo.com>
Subject: Re: [PATCH] init, fix initcall blacklist for modules
Date: Tue, 14 Jun 2016 05:59:46 -0400	[thread overview]
Message-ID: <575FD592.2020303@redhat.com> (raw)
In-Reply-To: <87bn34ls9w.fsf@rasmusvillemoes.dk>



On 06/13/2016 04:59 PM, Rasmus Villemoes wrote:
> On Mon, Jun 13 2016, Prarit Bhargava <prarit@redhat.com> 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 blacklisting code will now always fail when
> 
> I was and am pretty sure that %pf ends up using
> sprint_symbol_no_offset(), so I don't see how this is new. But maybe
> "now" doesn't refer to c8cdd2be21?

Oops.  I can see how you read that that way.  No, this isn't caused by or
"Fixes:" c8cdd2be21.  At some point "%pF" changed its behavior and blacklisting
module_init() functions stopped working.

P.

> 
>> comparing module_init() function names.  This patch resolves the issue by
>> comparing to the length of the function_name.
>>
>> Signed-off-by: Prarit Bhargava <prarit@redhat.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Thomas Gleixner <tglx@linutronix.de>
>> Cc: Yang Shi <yang.shi@linaro.org>
>> Cc: Ingo Molnar <mingo@kernel.org>
>> Cc: Mel Gorman <mgorman@suse.de>
>> Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
>> Cc: Kees Cook <keescook@chromium.org>
>> Cc: Yaowei Bai <baiyaowei@cmss.chinamobile.com>
>> Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>
>> ---
>>  init/main.c |   14 +++++++++++++-
>>  1 file changed, 13 insertions(+), 1 deletion(-)
>>
>> diff --git a/init/main.c b/init/main.c
>> index 4c17fda5c2ff..09a795e91efe 100644
>> --- a/init/main.c
>> +++ b/init/main.c
>> @@ -708,14 +708,26 @@ static bool __init_or_module initcall_blacklisted(initcall_t fn)
>>  {
>>  	struct blacklist_entry *entry;
>>  	char fn_name[KSYM_SYMBOL_LEN];
>> +	char *space;
>> +	int length;
>>  
>>  	if (list_empty(&blacklisted_initcalls))
>>  		return false;
>>  
>>  	sprint_symbol_no_offset(fn_name, (unsigned long)fn);
>> +	/*
>> +	 * fn will be "function_name [module_name]" where [module_name] is not
>> +	 * displayed for built-in initcall functions.  Strip off the
>> +	 * [module_name].
>> +	 */
>> +	space = strchrnul(fn_name, ' ');
>> +	if (!space)
>> +		length = strlen(fn_name);
>> +	else
>> +		length = space - fn_name;
> 
> strchrnul never returns NULL, so this could just be 'length =
> strchrnul(fn_name, ' ') - fn_name;'. But I don't think that's what you
> want anyway: Suppose one has blacklisted "init_foobar", and the function
> pointer resolves to a completely unrelated "init_foo", we'll end up
> falsely also blacklisting that since we're just comparing prefixes.
> 
> May I suggest
> 
>   strreplace(fn_name, ' ', '\0');
> 
> which also seems to match the comment a little better (and eliminates
> the extra variables and the hunk below).
> 
>>  	list_for_each_entry(entry, &blacklisted_initcalls, next) {
>> -		if (!strcmp(fn_name, entry->buf)) {
>> +		if (!strncmp(fn_name, entry->buf, length)) {
>>  			pr_debug("initcall %s blacklisted\n", fn_name);
>>  			return true;
>>  		}
> 
> Rasmus
> 

  reply	other threads:[~2016-06-14  9:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-13 12:29 [PATCH] init, fix initcall blacklist for modules Prarit Bhargava
2016-06-13 20:59 ` Rasmus Villemoes
2016-06-14  9:59   ` Prarit Bhargava [this message]
2016-06-14 22:31     ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2016-06-13 12:27 Prarit Bhargava

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=575FD592.2020303@redhat.com \
    --to=prarit@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=baiyaowei@cmss.chinamobile.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=yang.shi@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox