Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965000AbVJUQYM (ORCPT ); Fri, 21 Oct 2005 12:24:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965019AbVJUQYM (ORCPT ); Fri, 21 Oct 2005 12:24:12 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:56526 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S965000AbVJUQYJ (ORCPT ); Fri, 21 Oct 2005 12:24:09 -0400 Subject: Re: Understanding Linux addr space, malloc, and heap From: Arjan van de Ven To: "Vincent W. Freeh" Cc: linux-kernel@vger.kernel.org In-Reply-To: <4359119E.6050407@csc.ncsu.edu> References: <4358F0E3.6050405@csc.ncsu.edu> <1129903396.2786.19.camel@laptopd505.fenrus.org> <4359051C.2070401@csc.ncsu.edu> <1129908179.2786.23.camel@laptopd505.fenrus.org> <43590B23.2090101@csc.ncsu.edu> <1129909719.2786.27.camel@laptopd505.fenrus.org> <4359119E.6050407@csc.ncsu.edu> Content-Type: text/plain Date: Fri, 21 Oct 2005 18:23:59 +0200 Message-Id: <1129911840.2786.29.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-Spam-Score: 2.9 (++) X-Spam-Report: SpamAssassin version 3.0.4 on pentafluge.infradead.org summary: Content analysis details: (2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.1 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address [80.57.133.107 listed in dnsbl.sorbs.net] 2.8 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org [] X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 635 Lines: 16 On Fri, 2005-10-21 at 12:04 -0400, Vincent W. Freeh wrote: > Clearly, it was a mistake to post that code. I had no idea so many > people would point out the bleeding obvious. > > Here is a more elaborate version--that does the same thing, but more > lines of code. In it malloc'd memory is mprotect'd. The program > generates a SIGSEGV, a page fault. ... and what is the problem ? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/