From owner-freebsd-emulation@FreeBSD.ORG Mon Jan 22 17:45:38 2007 Return-Path: X-Original-To: freebsd-emulation@FreeBSD.org Delivered-To: freebsd-emulation@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5127E16A402 for ; Mon, 22 Jan 2007 17:45:38 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.freebsd.org (Postfix) with ESMTP id 0C95013C44B for ; Mon, 22 Jan 2007 17:45:37 +0000 (UTC) (envelope-from jkim@FreeBSD.org) Received: from niksun.com (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id l0MHjapf055932 for ; Mon, 22 Jan 2007 12:45:37 -0500 (EST) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-emulation@FreeBSD.org Date: Mon, 22 Jan 2007 12:45:26 -0500 User-Agent: KMail/1.6.2 References: <200701191851.08685.jkim@FreeBSD.org> <200701200205.41517.jkim@FreeBSD.org> In-Reply-To: <200701200205.41517.jkim@FreeBSD.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <200701221245.29294.jkim@FreeBSD.org> X-Virus-Scanned: ClamAV 0.88.6/2477/Mon Jan 22 10:10:05 2007 on anuket.mj.niksun.com X-Virus-Status: Clean Cc: Subject: Re: A new mmap finger printer X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2007 17:45:38 -0000 On Saturday 20 January 2007 02:05 am, Jung-uk Kim wrote: > On Friday 19 January 2007 06:51 pm, Jung-uk Kim wrote: > > I added PROT_EXEC test and cleaned up Marcin Cieslak's mmap > > finger printer. Can any one try this on a real Linux/i386 box > > and send me the output? > > http://people.freebsd.org/~jkim/mmap_test.c I realized each distro has different mmap behavior. :-( The following is the list of quirks that I found: 1. READ implies EXEC on some distros. 2. EXEC implies READ on some distros. 3. WRITE implies READ on some distros. 4. WRITE implies EXEC on some distros. Obviously we want maximum compatibility. So, I think we have to do all of the above. Actually I found that's what Linux/ia64 does for ia32 emulation. ;-) Thank you all for the reports! Jung-uk Kim