Re: ZFS ABD Panic

On Tue, Jun 27, 2017 at 10:25:16AM -0400, Shawn Webb wrote:
> On Tue, Jun 27, 2017 at 05:22:39PM +0300, Andriy Gapon wrote:
> > On 27/06/2017 17:16, Shawn Webb wrote:
> > > On Tue, Jun 27, 2017 at 05:12:01PM +0300, Andriy Gapon wrote:
> > >> On 26/06/2017 03:31, Shawn Webb wrote:
> > >>> This is on the latest HardenedBSD 12-CURRENT on one of my servers:
> > >>>
> > >>> [141] panic: sleepq_add: td 0xfffff80008d20560 to sleep on wchan 0xfffff803b7d4e810 with sleeping prohibited
> > >>> [141] cpuid = 5
> > >>> [141] time = 1498436043
> > >>> [141] KDB: stack backtrace:
> > >>> [141] db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00002fc8b0
> > >>> [141] vpanic() at vpanic+0x19c/frame 0xfffffe00002fc930
> > >>> [141] kassert_panic() at kassert_panic+0x126/frame 0xfffffe00002fc9a0
> > >>> [141] sleepq_add() at sleepq_add+0x34f/frame 0xfffffe00002fc9f0
> > >>> [141] _sx_xlock_hard() at _sx_xlock_hard+0x2a4/frame 0xfffffe00002fcaa0
> > >>> [141] _sx_xlock() at _sx_xlock+0x98/frame 0xfffffe00002fcae0
> > >>> [141] refcount_remove_many() at refcount_remove_many+0x2a/frame 0xfffffe00002fcb20
> > >>> [141] abd_return_buf() at abd_return_buf+0xe3/frame 0xfffffe00002fcb50
> > >>> [141] vdev_geom_io_intr() at vdev_geom_io_intr+0x114/frame 0xfffffe00002fcb70
> > >>> [141] g_io_schedule_up() at g_io_schedule_up+0x42/frame 0xfffffe00002fcba0
> > >>> [141] g_up_procbody() at g_up_procbody+0x6d/frame 0xfffffe00002fcbb0
> > >>> [141] fork_exit() at fork_exit+0x84/frame 0xfffffe00002fcbf0
> > >>> [141] fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe00002fcbf0
> > >>
> > >> Seems like another architectural incompatibility between illumos and FreeBSD.
> > >> Are you able to reproduce the crash more or less reliably?
> > > 
> > > Yup. I just need to do a buildworld and it's triggered.
> > > 
> > 
> > Could you please test this patch?
> > http://dpaste.com/12M183A.txt
> > I put it together rather quickly, but I think that it should work :)
> 
> Can do later today. I'll report back either tonight or tomorrow.

That seems to have fixed it! No kernel panic as of yet. It has survived
two world + kernel builds.

Thanks a lot for the help!

-- 
Shawn Webb
Cofounder and Security Engineer
HardenedBSD

GPG Key ID:          0x6A84658F52456EEE
GPG Key Fingerprint: 2ABA B6BD EF6A F486 BE89  3D9E 6A84 658F 5245 6EEE