NetBSD-Bugs archive

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

kern/56599: librump has unresolved symbols from rumps



>Number:         56599
>Category:       kern
>Synopsis:       librump has unresolved symbols from rumps
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Jan 03 00:45:00 +0000 2022
>Originator:     Valery Ushakov
>Release:        NetBSD-9.99.92
>Organization:
>Environment:
NetBSD nb 9.99.92 NetBSD 9.99.92 (GENERIC) #0: Thu Nov 18 15:58:42 MSK 2021  uwe@majava:/home/uwe/work/netbsd/cvs/src/sys/arch/amd64/compile/GENERIC amd64
>Description:
librump should be self-contained w.r.t. symbols in rumpns namespace,
i.e.

  $ nm -u /usr/lib/librump.so | grep rumpns
  $

should be empty.  But on current we have quite a few dependencies
that snuck in:

  $ nm -u librump.so | grep rumpns
                   U rumpns_dead_vnodeop_p
                   U rumpns_fs_filtops
                   U rumpns_holdrelel
                   U rumpns_pnbuf_cache
                   U rumpns_ubc_uiomove
                   U rumpns_uvm_vnodeops
                   U rumpns_vhold
                   U rumpns_vn_lock

I haven't checked all of these, but e.g. 

  sys_descrip.c,v 1.38 2021/09/11 10:09:13 riastradh
  vnode_if.c,v 1.115 2021/10/20 03:13:14 thorpej

are some of the offenders.

We probably get away with it b/c most rump tests in the tree link with
-lrumpvfs.  Linking them statically will probably fail b/c of
cross-lib dependencies (I haven't tried).

I noticed this b/c I'm rumpifying wscons vt100 emulation and it's
self-contained and should not need anything besides -lrump -lrumpuser,
but I have to also link with -lrumpvfs -lrumpvfs_nofifofs

>How-To-Repeat:
$ nm -u librump.so | grep rumpns

>Fix:



Home | Main Index | Thread Index | Old Index