NetBSD Problem Report #54151

From paul@whooppee.com  Thu May  2 11:14:09 2019
Return-Path: <paul@whooppee.com>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id A14257A0D9
	for <gnats-bugs@gnats.NetBSD.org>; Thu,  2 May 2019 11:14:09 +0000 (UTC)
Message-Id: <20190502111407.2BE3730F2C2@speedy.whooppee.com>
Date: Thu,  2 May 2019 19:14:07 +0800 (PST)
From: paul@whooppee.com
Reply-To: paul@whooppee.com
To: gnats-bugs@NetBSD.org
Subject: COMPAT_50 doesn't work for ``route monitor''
X-Send-Pr-Version: 3.95

>Number:         54151
>Category:       kern
>Synopsis:       COMPAT_50 doesn't work for ``route monitor''
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu May 02 11:15:00 +0000 2019
>Originator:     Paul Goyette
>Release:        NetBSD 8.99.37
>Organization:
+--------------------+--------------------------+-----------------------+
| Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
| (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul@whooppee.com     |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette@netbsd.org   |
+--------------------+--------------------------+-----------------------+
>Environment:


System: NetBSD speedy.whooppee.com 8.99.37 NetBSD 8.99.37 (SPEEDY 2019-04-24 23:45:06 UTC) #0: Thu Apr 25 09:00:09 UTC 2019 paul@speedy.whooppee.com:/build/netbsd-local/obj/amd64/sys/arch/amd64/compile/SPEEDY amd64
Architecture: x86_64
Machine: amd64
>Description:
A NetBSD-5.2 version of the ``route monitor'' command fails on current
NetBSD kernels, producing no output.

>How-To-Repeat:
1. Build a release, and install it (qemu VM is fine)
2. Create a /chroot52 directory, and unpack the base.tgz from NetBSD-5.2
3. Boot the result, login as root, and execute the commands

	# chroot /chroot52 route monitor &
	# ifconfig lo0 alias 1.2.3.4

4. A working system will display a couple of routing table update messages
   such as

	RTM_ONEWADDR
	got message of size 152 on Wed May  1 04:43:57 2019
	RTM_ADD: Add Route: len 152, pid 463, seq 0, errno 0, flags: <UP,HOST> locks:  inits:
	sockaddrs: <DST,GATEWAY>
	 1.2.3.4 lo0

   while a broken system displays nothing.

   A manual bisect shows that the ``route monitor'' command produces
   correct output with kernels built up to 2017-04-11 at 13:50 UTC.  With
   a newer kernel built from 14:00 or later, no output is produced.  Only
   one commit was made in that brief interval:

	Module Name:	src
	Committed By:	roy
	Date:		Tue Apr 11 13:55:55 UTC 2017

	Modified Files:
		src/share/man/man4: route.4
		src/sys/net: raw_cb.h raw_usrreq.c route.h rtsock.c

	Log Message:
	Add RO_MSGFILTER socket option to PF_ROUTE to filter out
	un-wanted route(4) messages.

	Inspired by the ROUTE_MSGFILTER equivalent in OpenBSD,
	but with an API which allows the full range of potential
	message types.

>Fix:


>Unformatted:

Home	PR Database Search