All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Morton Andrew Morton <akpm@osdl.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	ak@suse.de, vgoyal@in.ibm.com, linux-kernel@vger.kernel.org,
	fastboot@lists.osdl.org,
	Fernando Luis Vazquez Cao <fernando@intellilink.co.jp>
Subject: Re: [PATCH 1/5] stack overflow safe kdump (2.6.15-i386) - safe_smp_processor_id
Date: Fri, 20 Jan 2006 08:23:18 -0500	[thread overview]
Message-ID: <20060120132318.GI4695@in.ibm.com> (raw)
In-Reply-To: <1137417824.2256.85.camel@localhost.localdomain>

On Mon, Jan 16, 2006 at 10:23:44PM +0900, Fernando Luis Vazquez Cao wrote:
> On the event of a stack overflow critical data that usually resides at
> the bottom of the stack is likely to be stomped and, consequently, its
> use should be avoided.
> 
> In particular, in the i386 and IA64 architectures the macro
> smp_processor_id ultimately makes use of the "cpu" member of struct
> thread_info which resides at the bottom of the stack. x86_64, on the
> other hand, is not affected by this problem because it benefits from
> the use of the PDA infrastructure.
> 
> To circumvent this problem I suggest implementing
> "safe_smp_processor_id()" (it already exists in x86_64) for i386 and
> IA64 and use it as a replacement for smp_processor_id in the reboot path
> to the dump capture kernel. This is a possible implementation for i386.
> 

Acked-by: Vivek Goyal <vgoyal@in.ibm.com>

> ---
> diff -urNp linux-2.6.15/arch/i386/kernel/smp.c
> linux-2.6.15-sov/arch/i386/kernel/smp.c
> --- linux-2.6.15/arch/i386/kernel/smp.c	2006-01-03 12:21:10.000000000
> +0900
> +++ linux-2.6.15-sov/arch/i386/kernel/smp.c	2006-01-16
> 20:25:50.000000000 +0900
> @@ -628,3 +628,28 @@ fastcall void smp_call_function_interrup
>  	}
>  }
>  
> +static int convert_apicid_to_cpu(int apic_id)
> +{
> +	int i;
> +
> +	for (i = 0; i < NR_CPUS; i++) {
> +		if (x86_cpu_to_apicid[i] == apic_id)
> +		return i;
> +	}
> +	return -1;
> +}
> +
> +int safe_smp_processor_id(void) {
> +	int apicid, cpuid;
> +
> +	if (!boot_cpu_has(X86_FEATURE_APIC))
> +		return 0;
> +
> +	apicid = hard_smp_processor_id();
> +	if (apicid == BAD_APICID)
> +		return 0;
> +
> +	cpuid = convert_apicid_to_cpu(apicid);
> +
> +	return cpuid >= 0 ? cpuid : 0;
> +}
> diff -urNp linux-2.6.15/include/asm-i386/smp.h
> linux-2.6.15-sov/include/asm-i386/smp.h
> --- linux-2.6.15/include/asm-i386/smp.h	2006-01-03 12:21:10.000000000
> +0900
> +++ linux-2.6.15-sov/include/asm-i386/smp.h	2006-01-16
> 20:25:50.000000000 +0900
> @@ -90,12 +90,14 @@ static __inline int logical_smp_processo
>  
>  #endif
>  
> +extern int safe_smp_processor_id(void);
>  extern int __cpu_disable(void);
>  extern void __cpu_die(unsigned int cpu);
>  #endif /* !__ASSEMBLY__ */
>  
>  #else /* CONFIG_SMP */
>  
> +#define safe_smp_processor_id() 0
>  #define cpu_physical_id(cpu)		boot_cpu_physical_apicid
>  
>  #define NO_PROC_ID		0xFF		/* No processor magic marker */
> 
> 

      reply	other threads:[~2006-01-20 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16 13:23 [PATCH 1/5] stack overflow safe kdump (2.6.15-i386) - safe_smp_processor_id Fernando Luis Vazquez Cao
2006-01-20 13:23 ` Vivek Goyal [this message]

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=20060120132318.GI4695@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=fernando@intellilink.co.jp \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.