18:48:52 warden: Maybe https://www.illumos.org/issues/17584 is related? 18:48:53 → BUG 17584: Null pointer leading to a crash when using NAT66 (New) 18:49:45 And possibly https://www.illumos.org/issues/15555 18:49:46 → BUG 15555: ipf: NULL pointer dereference in fr_tcp_age() / fr_movequeue() (New) 18:50:33 rzezeski: For the stack frame thing, https://www.illumos.org/issues/17585 18:50:33 → FEATURE 17585: MDB should look past mutex_enter() and find the real stack frame (New) 19:28:09 jclulow: that looks like the same issue to me (17584), though based on warden's mdb I think I confirmed oifq != NULL, and that would suggest nifq is. Given the logic in fr_tcp_age() to derive nifq, I would not be surprised. 19:28:35 rzezeski: There is some mention of that being the case in 15555 too 19:28:39 that would be an annoying one to verify over IRC 19:28:53 It's almost certainly a race because we're not locking the thing 19:28:57 in some subset of cases 19:28:57 yea 19:29:22 I'm not sure why I've never seen this, I have a lot of ipf-based NAT stuff going on 19:29:30 But maybe it's because I don't allow IPv6 in the house 19:29:58 IPv6 does tend to find sharp edges in our code, though it's getting better 19:30:31 this was my first time looking into ipf code, and I'm sure there's history there but man this could really be cleaned up 19:31:00 looks like it was meant to compile from source in all sorts of different contexts 19:31:12 the macro-soup is certainly hard on the eyes 21:11:00 I wish I could win the lotto and spend all my time bringing up vxlnat^H^H^H^H^H^H knat. (The secret sauce is use of `conn_t`!) 21:11:18 rzezeski: you are correct regarding ipf's "single-source for all platforms" philosophy. 23:49:46 Sorry I didn’t replay sooner… we are in different TZ (CEST here) and this evening I has been away for a meeting 23:51:48 I confirm I’m using IPv6 and NAT too… it make sense for me that bugs referenced by jclulow are related to my issue 23:55:49 Tomorrow I’ll post info about my ipf configuration. Thanks to you all until now. Surely I’m with rzezeski: troubleshooting such a problem via IRC doesn’t look viable! :)