Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 03 Sep 2019 14:07:24 -0000
From:      Hans Petter Selasky <hps@selasky.org>
To:        Kristof Provost <kp@FreeBSD.org>, Enji Cooper <yaneurabeya@gmail.com>
Cc:        src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org>, FreeBSD CURRENT <freebsd-current@freebsd.org>
Subject:   Re: Panic with r346530 [Re: svn commit: r346530 - in head/sys: netinet netinet6]
Message-ID:  <89bdecf9-970e-f571-a94d-b4ceaea18368@selasky.org>
In-Reply-To: <1342BBD2-EE0F-4457-8752-659EA7F01725@FreeBSD.org>
References:  <201904220727.x3M7ROpR009729@repo.freebsd.org> <2F3D6B17-AF4F-4B0F-B20E-5EF41DE851F9@gmail.com> <87917500-0381-79d8-a34b-819848abed32@selasky.org> <f2567fc6-fd5b-67c9-a994-5a48d65d1278@selasky.org> <8EAC0CFE-E22F-478F-813F-A07E68C0518D@gmail.com> <1342BBD2-EE0F-4457-8752-659EA7F01725@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 4/22/19 3:28 PM, Kristof Provost wrote:
> On 22 Apr 2019, at 12:25, Enji Cooper wrote:
>> Either the sys/netinet/ or sys/netipsec/ tests triggered the panic. 
>> Not sure which right now.
>>
> That looks to be happening during a vnet jail teardown, so it’s likely 
> the sys/netipsec or sys/netpfil/pf tests.
> 
> I’ve done a quick test with the pf tests, and they provoke this panic:
> 
>      panic: mtx_lock() of destroyed mutex @ 
> /usr/src/sys/netinet/ip_reass.c:628
>      cpuid = 0
>      time = 1555939645
>      KDB: stack backtrace:
>      db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 
> 0xfffffe0091d68530
>      vpanic() at vpanic+0x19d/frame 0xfffffe0091d68580
>      panic() at panic+0x43/frame 0xfffffe0091d685e0
>      __mtx_lock_flags() at __mtx_lock_flags+0x12e/frame 0xfffffe0091d68630
>      ipreass_cleanup() at ipreass_cleanup+0x86/frame 0xfffffe0091d68670
>      if_detach_internal() at if_detach_internal+0x786/frame 
> 0xfffffe0091d686f0
>      if_detach() at if_detach+0x3d/frame 0xfffffe0091d68710
>      lo_clone_destroy() at lo_clone_destroy+0x16/frame 0xfffffe0091d68730
>      if_clone_destroyif() at if_clone_destroyif+0x21f/frame 
> 0xfffffe0091d68780
>      if_clone_detach() at if_clone_detach+0xb8/frame 0xfffffe0091d687b0
>      vnet_loif_uninit() at vnet_loif_uninit+0x26/frame 0xfffffe0091d687d0
>      vnet_destroy() at vnet_destroy+0x124/frame 0xfffffe0091d68800
>      prison_deref() at prison_deref+0x29d/frame 0xfffffe0091d68840
>      sys_jail_remove() at sys_jail_remove+0x28f/frame 0xfffffe0091d68890
>      amd64_syscall() at amd64_syscall+0x276/frame 0xfffffe0091d689b0
>      fast_syscall_common() at fast_syscall_common+0x101/frame 
> 0xfffffe0091d689b0
>      --- syscall (508, FreeBSD ELF64, sys_jail_remove), rip = 
> 0x80031e12a, rsp = 0x7fffffffe848, rbp = 0x7fffffffe8d0 ---
>      KDB: enter: panic
>      [ thread pid 1223 tid 100501 ]
>      Stopped at      kdb_enter+0x3b: movq    $0,kdb_why
>      db>
> 
> To reproduce:
> 
>      kldload pfsync
>      cd /usr/tests/sys/netpfil/pf
>      sudo kyua test
> 

I'll revert r346530 until further testing has taken place.

Thank you!

--HPS






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89bdecf9-970e-f571-a94d-b4ceaea18368>