Re: Kernel panic related to pipe

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

mlelstv%serpens.de@localhost (Michael van Elst) writes:

>martin%duskware.de@localhost (Martin Husemann) writes:

>>	KASSERT(mutex_owned(pipe->pipe_lock));

>>with a NULL deref as apparently "pipe" is NULL.



>A amd64 XEN3_DOM0 kernel seems to be unaffected.

>tazz: {4} ident /netbsd_xen|grep sys_pipe
>     $NetBSD: sys_pipe.c,v 1.177 2026/10/03 16:28:30 riastradh Exp $


A regular kernel on the same machine also doesn't panic. The CPU is
an old dual core with hyperthreading.

[     1.000003] cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, id 0x206a7
[     1.000003] cpu0: node 0, package 0, core 0, smt 0