Re: kern/56232: Unstable system with tar on /dev

[mlelstv%serpens.de@localhost (Michael van Elst)]

The following reply was made to PR kern/56232; it has been noted by GNATS.

From: mlelstv%serpens.de@localhost (Michael van Elst)
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/56232: Unstable system with tar on /dev
Date: Fri, 4 Jun 2021 14:13:35 -0000 (UTC)

 rvp%SDF.ORG@localhost (RVP) writes:
 
 > - In sys/dev/pad/pad.c, padattach() doesn't seem to be called from 
 > anywhere
 >    and therefore mutex_init() is never called.
 
 pad is a pseudo device, part of the code calling the attach function
 is autogenerated by config(1) when building a kernel.
 
 >    `pad_ca' is used in 2 places, but is defined nowhere.
 
 It is defined by the CFATTACH_ECL2_NEW macro in sys/device.h.
 
 
 > - Similarly, in sys/net/if_tap.c, tapattach() is not called by anybody.
 
 dito.
 
 When you look into the compile directory after a build, you see the generated
 file ioconf.c.
 
 The table 'pdevinit[]' lists all the pseudodevice attach routines that
 will be called by config_finalize() in sys/kern/subr_autoconf.c.
 
 
 Greetings,