From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 25 May 2001 10:04:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 25 May 2001 10:04:43 -0400 Received: from [195.180.174.187] ([195.180.174.187]:1920 "EHLO idun.neukum.org") by vger.kernel.org with ESMTP id ; Fri, 25 May 2001 10:04:34 -0400 Content-Type: text/plain; charset=US-ASCII From: Oliver Neukum To: Keith Owens , Andreas Dilger Subject: Re: [CHECKER] large stack variables (>=1K) in 2.4.4 and 2.4.4-ac8 Date: Fri, 25 May 2001 16:03:57 +0200 X-Mailer: KMail [version 1.2] Cc: Andi Kleen , linux-kernel@vger.kernel.org In-Reply-To: <24688.990773627@kao2.melbourne.sgi.com> In-Reply-To: <24688.990773627@kao2.melbourne.sgi.com> MIME-Version: 1.0 Message-Id: <01052516035700.01561@idun> Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > A small overflow of the kernel stack overwrites the struct task at the > bottom of the stack, recovery is dubious at best because we rely on > data in struct task. A large overflow of the kernel stack either > corrupts the storage below this task's stack, which could hit anything, > or it gets a stack fault. Is there a reason for the task structure to be at the bottom rather than the top of these two pages ? Regards Oliver