enc(4) uninitialized in -current?

[John Baldwin]

On Thursday, September 27, 2012 9:02:59 am Marcin Cieslak wrote:
> >> John Baldwin <jhb at freebsd.org> wrote:
> > On Wednesday, September 26, 2012 6:42:19 pm Garrett Cooper wrote:
> >> On Wed, Sep 26, 2012 at 3:33 PM, Olivier Cochard-Labbé
> >> <olivier at cochard.me> wrote:
> >> > On Thu, Sep 27, 2012 at 12:10 AM, Marcin Cieslak <saper at saper.info> wrote:
> >> >> I have just updated by 9.0-something laptop to 10.0-CURRENT r240948
> >> >> and it very quickly panics after enabling network with IPsec
> >> >> (I am using IPsec w/racoon for IPv4 over 802.11, also using
> >> >> tunelled IPv6).
> >> >
> >> > I don't know if it's related, but one of the first dmesg message
> >> > displayd on my -current (rev 240921) is:
> >> >
> >> > module_register: module enc already exists!
> >> > Module enc failed to register: 17
> >
> > I suspect this is the root cause and that the "wrong" global variable is being 
> > used in ipsec_output.c due to duplicate symbols.
> 
> As the original poster: I don't have this "module enc already exists!" message.
> I have had "device enc" in the kernel config file and I didn't try
> to load if_enc as module. I have IPSEC permanently enabled
> in the kernel and it is initialized at boot with setkey and later
> with racoon. 
> 
> > OTOH, have you created an enc0 device?  I can't find anything that 
> > automatically creates it.
> 
> No. Previously, in 9.x times, it was always present in the ifconfig output.

Ok, I think that is the root cause.

HEAD should still be creating an enc0.  The enc.c file creates an enc_cloner:

IFC_SIMPLE_DECLARE(enc, 1);

static int
enc_modevent(module_t mod, int type, void *data)
{
	switch (type) {
	case MOD_LOAD:
		mtx_init(&enc_mtx, "enc mtx", NULL, MTX_DEF);
		if_clone_attach(&enc_cloner);
		break;

That '1' is the minimum number of interfaces to create on attach in
ifc_simple_attach().  I've no idea why enc0 isn't being created on boot, but
it should be.

-- 
John Baldwin