public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	kgdb-bugreport@lists.sourceforge.net,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kgdb: Replace strstr() by strchr() for single-character needles
Date: Sat, 12 Sep 2009 10:16:17 -0500	[thread overview]
Message-ID: <4AABBB41.40208@windriver.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0909112214370.15464@ayla.of.borg>

I think the patch is fine and I will accept it into the kgdb tree for
pushing to Linus, but I did have a question.

How did the kgdbts.o end up getting compiled on m68k if there is no kgdb
support on m68k?

CONFIG_KGDB_TESTS should not be able to be set if there is no
CONFIG_KGDB set.

Thanks,
Jason.


Geert Uytterhoeven wrote:
> Some versions of gcc replace calls to strstr() with single-character
> "needle" string parameters by calls to strchr() behind our back.
> This causes linking errors if strchr() is defined as an inline function
> in <asm/string.h> (e.g. on m68k, which BTW doesn't have kgdb support).
>
> Prevent this by explicitly calling strchr() instead.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
> This is the single remaining case where strstr() is used with a
> single-character needle.  Cfr.
> commit 0d03d59d9b31cd1e33b7e46a80b6fef66244b1f2 ("md: Fix "strchr"
> [drivers/md/dm-log-userspace.ko] undefined!")
> commit d8b0fb51ef1563c631d26cb649a5479b5cc4899c ("[PATCH] libertas link error
> due to gcc `smartness'")
>
>  drivers/misc/kgdbts.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/misc/kgdbts.c b/drivers/misc/kgdbts.c
> index e4ff50b..2a43d8c 100644
> --- a/drivers/misc/kgdbts.c
> +++ b/drivers/misc/kgdbts.c
> @@ -885,16 +885,16 @@ static void kgdbts_run_tests(void)
>  	int nmi_sleep = 0;
>  	int i;
>  
> -	ptr = strstr(config, "F");
> +	ptr = strchr(config, 'F');
>  	if (ptr)
>  		fork_test = simple_strtol(ptr + 1, NULL, 10);
> -	ptr = strstr(config, "S");
> +	ptr = strchr(config, 'S');
>  	if (ptr)
>  		do_sys_open_test = simple_strtol(ptr + 1, NULL, 10);
> -	ptr = strstr(config, "N");
> +	ptr = strchr(config, 'N');
>  	if (ptr)
>  		nmi_sleep = simple_strtol(ptr+1, NULL, 10);
> -	ptr = strstr(config, "I");
> +	ptr = strchr(config, 'I');
>  	if (ptr)
>  		sstep_test = simple_strtol(ptr+1, NULL, 10);
>  
>   


  reply	other threads:[~2009-09-12 15:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 20:16 [PATCH] kgdb: Replace strstr() by strchr() for single-character needles Geert Uytterhoeven
2009-09-12 15:16 ` Jason Wessel [this message]
2009-09-13  7:40   ` Geert Uytterhoeven

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=4AABBB41.40208@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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