Subject: kern/2582: "route change default -mtu 1500" panics
To: None <gnats-bugs@NetBSD.ORG>
From: John Hawkinson <jhawk@mit.edu>
List: netbsd-bugs
Date: 06/30/1996 16:56:30
>Number: 2582
>Category: kern
>Synopsis: "route change default -mtu 1500" panics
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: kern-bug-people (Kernel Bug People)
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jun 30 17:20:01 1996
>Last-Modified:
>Originator: John Hawkinson
>Organization:
MIT SIPB
>Release: 1.1
>Environment:
Seen on LIMEKILLER (1.1) built Sat May 11 17:43, also seen on ZORKMID
(1.2_ALPHA) built from sources supped on 15 Jun.
>Description:
Running "route change default -mtu 1500" causes a panic.
Running "route change -mtu 1500 default <NEXT-HOP>" works
fine.
>How-To-Repeat:
[typos mine; ?'s hex numbers not worth typing (ostensibly)]
# route change default -mtu 1500
kernel: page fault trrap, code = 0
Stopped at _ifa_ifwithnet+0x13
db> t
ifa_ifwithnet(0,?,60,?,?) at ifa_ifwithnet+0x13
ifa_ifwithroute(803,?,0,?,0) at ifa_ifwithroute+0x45
route_output(?,?,?,c0000000,?) at route_output+0x401
raw_usrreq(?,9,?,0,0) at raw_usrreq+0x13a
route_usrreq(?,0,?,0,0) at sosend+0x58d
soo_write(?,?,?,?) at soo_write+0x19
sys_write(?,?,?,0,1a0dc) at sys_write+0xa4
syscall() at syscall+0x260
--- syscall (number 4)
>Fix:
Umm, don't _do_ that? Just use the right syntax?
I'm sorry I'm too lame to come up w/ a fix right now, but
a lacking PR is better than no PR, right?
>Audit-Trail:
>Unformatted: