From owner-freebsd-current Fri Jul 27 7:49:58 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 0C84D37B403; Fri, 27 Jul 2001 07:49:55 -0700 (PDT) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.4/8.11.2) id f6REni269151; Fri, 27 Jul 2001 07:49:44 -0700 (PDT) (envelope-from dillon) Date: Fri, 27 Jul 2001 07:49:44 -0700 (PDT) From: Matt Dillon Message-Id: <200107271449.f6REni269151@earth.backplane.com> To: Ian Dowse Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: SIGCHLD changes causing fault on nofault entry panics References: <200107271451.aa00148@salmon.maths.tcd.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :In the vmcore I just got, the panic occurred in the following :fragment in exit1(), when dereferencing p_sigacts (which is :p_procsig->ps_sigacts). I guess there is a race here if the parent :is exiting or something? : :+ if ((p->p_pptr->p_procsig->ps_flag & PS_NOCLDWAIT) :+ || p->p_pptr->p_sigacts->ps_sigact[_SIG_IDX(SIGCHLD)] == SIG_IGN) { : :Matt, I will just back out these changes from RELENG_4 shortly :until the issue is resolved. The change was non-essential and quite :contained, so it's probably better than waiting for a fix. : :Ian Ok, I'll take a look at it on the weekend and see if I can track down where the panic is coming from. I'll be that p_sigacts can wind up NULL in a reparenting case or something like that. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message