tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: COMPAT_50 vs NET_RT_IFLIST



I have removed the differences between 8.0 and -current but the
baseline problem still exists.  Someone more familiar with this
code will have to look into what broke between 5.2 and 8.0


On Mon, 29 Apr 2019, Paul Goyette wrote:

On Sat, 27 Apr 2019, Paul Goyette wrote:

So, I decided to try a little bit harder. I installed a stock 8.0 system in a qemu vm, and then loaded 5.2's base.tgz into a chroot directory.

Using the stock 8.0 ifconfig, I see
	# ifconfig -l
	wm0 lo0
	# ifconfig -a
	wm0: flags=0x8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
	        capabilities=2bf80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx>

		capabilities=2bf80<TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Tx>
	        capabilities=2bf80<UDP6CSUM_Tx>
	        enabled=0
	        ec_capabilities=7<VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU>
	        ec_enabled=0
	        address: 52:54:00:12:34:56
	        media: Ethernet autoselect (none)
	lo0: flags=0x8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33624
	        inet 127.0.0.1/8 flags 0x0
	        inet6 ::1/128 flags 0x20<NODAD>
	        inet6 fe80::1%lo0/64 flags 0x0 scopeid 0x2


When I chroot into the 5.2 directory, I get no output of any sort:

	# chroot /chroot-52/
	# ifconfig -l

	# ifconfig -a

So, there's definitely something wrong in 8.0 with the compat sysctl.

I probably changed the behavior with my work on the compat branch, which is likely why -current gets ENOENT errors.


OK, I dug a little bit further, and I know why there is a difference
between 8.0 and -current.  Yep, I broke it on the [pgoyette-compat]
branch.  I will see if I can fix it.  (Please note that real-life is
getting very complex right now, and I don't know how soon I will be
able to work on this.)

(Short version is that I removed the code that created multiple
versions of the sysctl nodes.)

I still cannot explain how things got broken between 5.2 and 8.0.  I
will defer to those who are more expert in this area than am I.  My
suspicion is that the breakage is related to sys/socket.h rev 1.99
which versioned AF_{,O}ROUTE for some 64-bit cleanliness.




+--------------------+--------------------------+-----------------------+
| Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
| (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
+--------------------+--------------------------+-----------------------+

!DSPAM:5cc665d0251011450219740!



+--------------------+--------------------------+-----------------------+
| Paul Goyette       | PGP Key fingerprint:     | E-mail addresses:     |
| (Retired)          | FA29 0E3B 35AF E8AE 6651 | paul%whooppee.com@localhost     |
| Software Developer | 0786 F758 55DE 53BA 7731 | pgoyette%netbsd.org@localhost   |
+--------------------+--------------------------+-----------------------+


Home | Main Index | Thread Index | Old Index