[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.02.1401301504380.12223@chino.kir.corp.google.com>
Date: Thu, 30 Jan 2014 15:05:23 -0800 (PST)
From: David Rientjes <rientjes@...gle.com>
To: Prarit Bhargava <prarit@...hat.com>
cc: linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>,
Michel Lespinasse <walken@...gle.com>,
Seiji Aguchi <seiji.aguchi@....com>,
Yang Zhang <yang.z.zhang@...el.com>,
Paul Gortmaker <paul.gortmaker@...driver.com>,
Janet Morgan <janet.morgan@...el.com>,
Tony Luck <tony.luck@...el.com>,
Ruiv Wang <ruiv.wang@...il.com>,
Gong Chen <gong.chen@...ux.intel.com>,
"H. Peter Anvin" <hpa@...ux.intel.com>, x86@...nel.org,
Fengguang Wu <fengguang.wu@...el.com>, yinghai@...nel.org,
tglx@...utronix.de, mingo@...e.hu, hpa@...or.com
Subject: Re: [PATCH] x86, cpu hotplug, Fix stack frame warning in
check_irq_vectors_for_cpu_disable()
On Tue, 28 Jan 2014, Prarit Bhargava wrote:
> Further discussion here: http://marc.info/?l=linux-kernel&m=139073901101034&w=2
>
> kbuild, 0day kernel build service, outputs the warning:
>
> arch/x86/kernel/irq.c:333:1: warning: the frame size of 2056 bytes
> is larger than 2048 bytes [-Wframe-larger-than=]
>
> because check_irq_vectors_for_cpu_disable() allocates two cpumasks on the
> stack. Fix this by moving the two cpumasks to a global file context.
>
> Signed-off-by: Prarit Bhargava <prarit@...hat.com>
Reported-by: Fengguang Wu <fengguang.wu@...el.com>
Tested-by: David Rientjes <rientjes@...gle.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists