From owner-freebsd-stable Wed Mar 20 12:19:11 2002 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4AA9B37B405; Wed, 20 Mar 2002 12:18:59 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.11.6/8.9.1) id g2KKIcT85692; Wed, 20 Mar 2002 12:18:38 -0800 (PST) (envelope-from dillon) Date: Wed, 20 Mar 2002 12:18:38 -0800 (PST) From: Matthew Dillon Message-Id: <200203202018.g2KKIcT85692@apollo.backplane.com> To: Jan Srzednicki Cc: freebsd-stable@FreeBSD.ORG, security-officer@FreeBSD.ORG Subject: request to MFC to security branch (was Re: reproducable panic with python) References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG RELENG_4_5 doex not have this patch. It probably should. I am CCing the security-officer. relevant information for security-officer: This is 1.213 (current) and 1.187.2.13 (stable) of vm/vm_map.c). It's a very simple and obvious patch. -Matt Matthew Dillon :> Yes, this has been fixed. Python was using MAP_ANON|MAP_NOSYNC :> mmap()'s and this resulted in the possibility of msync() encountering :> an optimized vm_map_entry that did not yet have a VM object associated :> with it, causing a panic. :> :> Both -stable and -current have been fixed to handle the case. :> -current was fixed on March 7th, and -stable on March 8th. : :Does that mean that RELENG_4_5 has that patched also? : :-- :Winfried :mail: winfried@dream.vg http://violent.dream.vg JS500-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message