From owner-freebsd-bugs  Wed Jul 24 06:50:03 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA19928
          for bugs-outgoing; Wed, 24 Jul 1996 06:50:03 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id GAA19920;
          Wed, 24 Jul 1996 06:50:01 -0700 (PDT)
Resent-Date: Wed, 24 Jul 1996 06:50:01 -0700 (PDT)
Resent-Message-Id: <199607241350.GAA19920@freefall.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org,
        zach@blizzard.gaffaneys.com
Received: from freebsd.gaffaneys.com (dialup2.gaffaneys.com [134.129.252.21])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id GAA19659
          for <FreeBSD-gnats-submit@freebsd.org>; Wed, 24 Jul 1996 06:44:36 -0700 (PDT)
Received: (from zach@localhost) by freebsd.gaffaneys.com (8.7.5/8.7.3) id IAA00279; Wed, 24 Jul 1996 08:45:37 -0500 (CDT)
Message-Id: <199607241345.IAA00279@freebsd.gaffaneys.com>
Date: Wed, 24 Jul 1996 08:45:37 -0500 (CDT)
From: Zach Heilig <zach@blizzard.gaffaneys.com>
Reply-To: zach@blizzard.gaffaneys.com
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/1423: route causes kernel page fault.
Sender: owner-bugs@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         1423
>Category:       kern
>Synopsis:       route causes kernel page fault.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 24 06:50:00 PDT 1996
>Last-Modified:
>Originator:     Zach Heilig
>Organization:
none
>Release:        FreeBSD 2.1.5-RELEASE i386
>Environment:

FreeBSD 2.1.5 (before the release was re-rolled)
	

>Description:

Running route can cause a kernel page fault.  I did a little bit of
tracking, and it seems to be faulting in the kernel copy of bcmp().  I
didn't have anyway to log the console message, so here are the related
pieces (the numbers that are there are in the order they were on the
screen, I may have omitted some trailing numbers that didn't look
interesting, and I abbreviated freely on my notepad):

Fatal trap 12: page fault while in kernel mode.
supervisor read, page not present.
ip: 0x8:0xf016f562
cs: 0x0:0xfffff,0x1b
cp: 165 (route)
im: net
<line stating a core dump failed...>

interesting output from 'nm -n /kernel':
f016f4e5 t cpystrflt_x
f016f508 T _copystr
f016f540 T _ffs
f016f54c T _bcmp
f016f574 T _lgdt
f016f598 T _lidt
f016f5a0 T _lldt

Obviously, it's not directly bcmp()'s fault.  A stack trace would be
more helpful (but I don't have one yet).

	

>How-To-Repeat:

$ route add default -link tun0

(is there a way to specify default traffic goes out tun0?)

	

>Fix:

Don't know.
	

>Audit-Trail:
>Unformatted: