From owner-freebsd-bugs@FreeBSD.ORG  Fri Jan  2 17:30:19 2015
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 24F0710B
 for <freebsd-bugs@FreeBSD.org>; Fri,  2 Jan 2015 17:30:19 +0000 (UTC)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0C60466306
 for <freebsd-bugs@FreeBSD.org>; Fri,  2 Jan 2015 17:30:19 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t02HUIcV059701
 for <freebsd-bugs@FreeBSD.org>; Fri, 2 Jan 2015 17:30:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 194974] Limit /dev/mem access to addresses in phys_avail[] -
 i.e. actual memory
Date: Fri, 02 Jan 2015 17:30:18 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: alc@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-194974-8-JEB9tZgC9E@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-194974-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-194974-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Jan 2015 17:30:19 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194974

Alan Cox <alc@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |alc@FreeBSD.org

--- Comment #2 from Alan Cox <alc@FreeBSD.org> ---
Use dump_avail[] rather than phys_avail[].  Between the time that we first
initialize phys_avail[] and finally execute vm_page_startup(), we remove pages
from phys_avail[] for various purposes.  Also, dump_avail[] includes pages
containing the kernel code and data that are excluded from phys_avail[].  In
summary, dump_avail[] more accurately describes the physical memory of the
machine.

See the arm version of this code.  It already implements the check against
dump_avail[].

-- 
You are receiving this mail because:
You are the assignee for the bug.