mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] markers: fix unchecked format
Date: Wed, 8 Oct 2008 00:05:08 -0400	[thread overview]
Message-ID: <20081008040508.GB31788@Krystal> (raw)
In-Reply-To: <48EC19A8.4010307@cn.fujitsu.com>

* Lai Jiangshan (laijs@cn.fujitsu.com) wrote:
> 
> when the second, third... probe is registered, its format is
> not checked, this patch fix it.
> 

It's already checked here :

marker_update_probes
  marker_update_probe_range
    set_marker
 
        if ((*entry)->format) {
                if (strcmp((*entry)->format, elem->format) != 0) {
                        printk(KERN_NOTICE
                                "Format mismatch for probe %s "
                                "(%s), marker (%s)\n",
                                (*entry)->name,
                                (*entry)->format,
                                elem->format);
                        return -EPERM;
                }
        } else {
                ret = marker_set_format(entry, elem->format);
                if (ret)
                        return ret;
        }

Given that marker_probe_register can be called to connect a probe to a
marker which does not exist yet (e.g. marker in a module not loaded), I
am not sure it makes sense to check for format string mismatch so early
in marker_probe_register (the moment it adds the marker to the hash
table). That's actually why I chose to leave it in later stage which
does the actual connection of the probes to the markers
(marker_update_probes).

If you really want to check it earlier, how do you plan to deal with
this scenario ?

1 - a marker probe is registered for markerA with format string
    "field1 %s"
2 - a module is loaded, which contains a marker markerA with format
    string "field1 %d"

I think it would be _really_ bad to make the module load fail because of
a marker format string mismatch... this is why I chose just to give a
warning in set_marker, which is shown when the markers are updated,
which happens when the module is loaded and when the marker hash table
is modified.

Mathieu

> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/marker.c b/kernel/marker.c
> index 4440a09..1196a6b 100644
> --- a/kernel/marker.c
> +++ b/kernel/marker.c
> @@ -651,11 +651,17 @@ int marker_probe_register(const char *name, const char *format,
>  	entry = get_marker(name);
>  	if (!entry) {
>  		entry = add_marker(name, format);
> -		if (IS_ERR(entry)) {
> +		if (IS_ERR(entry))
>  			ret = PTR_ERR(entry);
> -			goto end;
> -		}
> +	} else if (format) {
> +		if (!entry->format)
> +			ret = marker_set_format(&entry, format);
> +		else if (strcmp(entry->format, format))
> +			ret = -EPERM;
>  	}
> +	if (ret)
> +		goto end;
> +
>  	/*
>  	 * If we detect that a call_rcu is pending for this marker,
>  	 * make sure it's executed now.
> 
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2008-10-08  4:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-08  2:23 Lai Jiangshan
2008-10-08  4:05 ` Mathieu Desnoyers [this message]
2008-10-08  5:04   ` Lai Jiangshan
2008-10-09 13:46     ` Mathieu Desnoyers
2008-10-09 14:05       ` Ingo Molnar

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=20081008040508.GB31788@Krystal \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome