Fwd: [Re: cvs commit: src/sys/vm vm_map.c]

nectar_at_FreeBSD.org

Date: Wed, 5 May 2004 11:56:36 -0500
To: freebsd-security@FreeBSD.org, full-disclosure@lists.netsys.com, bugtraq@securityfocus.com


-- 
Jacques Vidrine <nectar@freebsd.org>
----- Forwarded message from Tim Robbins <tjr@freebsd.org> -----
Date: Tue, 23 Mar 2004 21:53:10 +1100
From: Tim Robbins <tjr@freebsd.org>
To: Pawel Jakub Dawidek <pjd@FreeBSD.org>
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sys/vm vm_map.c
Message-ID: <20040323105310.GA14855@cat.robbins.dropbear.id.au>
On Tue, Mar 23, 2004 at 11:33:00AM +0100, Pawel Jakub Dawidek wrote:
> On Tue, Mar 23, 2004 at 12:37:35AM -0800, Tim J. Robbins wrote:
> +> tjr         2004/03/23 00:37:34 PST
> +> 
> +>   FreeBSD src repository
> +> 
> +>   Modified files:
> +>     sys/vm               vm_map.c 
> +>   Log:
> +>   Do not copy vm_exitingcnt to the new vmspace in vmspace_exec(). Copying
> +>   it led to impossibly high values in the new vmspace, causing it to never
> +>   drop to 0 and be freed.
> 
> How serious it is? Do you planning to MFC it to RELENG_4 with peter@'s
> patch of course?
A user can cause the kernel to allocate an unbounded amount of wired
memory, causing the machine to panic or stop responding. It's been observed
to happen under real workloads; that is, the circumstances are not so
contrived that the bug could only be caused by a malicious user.
I don't have any immediate plans to MFC it (I don't have any 4.x systems
right now), but peter@ or ps@ may want to after letting it settle for a
while in -current.
Tim
----- End forwarded message -----
_______________________________________________
freebsd-security@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"

Fwd: [Re: cvs commit: src/sys/vm vm_map.c]

Relevant Pages