kern/54922: 9.99.45@20200202 panic: diagnostic assertion linux ldconfig triggers vpp != NULL in exit1()->radixtree.c line 674

[kardel%netbsg.org@localhost]

>Number:         54922
>Category:       kern
>Synopsis:       linux ldconfig triggers vpp != NULL in exit1()->radixtree.c line 674
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Feb 02 16:38:23 +0000 2020
>Originator:     Frank Kardel
>Release:        NetBSD 9.99.45
>Organization:
	
>Environment:
	
	
System: NetBSD pip 9.99.45 NetBSD 9.99.45 (PIPGEN) #1: Sun Feb 2 10:30:02 CET 2020 kardel@pip:/src/NetBSD/act/src/obj.amd64/sys/arch/amd64/compile/PIPGEN amd64
Architecture: x86_64
Machine: amd64
>Description:
	When bulk building pkgsrc from 20200202 on -current@20200202 a Linux binary ldconfig
	triggers in sys_exit()/exit1()/radix_tree_remove_node:674 the vpp != NULL assertion.
Stack (hand copied as usual ddb> sync trips over locking against myself (probably kernel_lock):
radix_tree_removenode()
exit1()
sys_exit()
linux_syscall()
Stopped in pid 4056.4056 (ldconfig) ata netbsd:breakpoint() ...

The LID of 4056 looks suspicious to me unless the is the new LID logic, but the would violate
a rustc assumption if I scanned the commit mails correctly.
>How-To-Repeat:
	Bulk build pkgsrc on a kernel from 20200202.
>Fix:
	?

>Unformatted: