From owner-freebsd-hackers Wed Jan 3 08:26:40 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA17363 for hackers-outgoing; Wed, 3 Jan 1996 08:26:40 -0800 (PST) Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA17347 for ; Wed, 3 Jan 1996 08:26:37 -0800 (PST) Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id IAA03649; Wed, 3 Jan 1996 08:26:36 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.7.3/8.6.5) with SMTP id JAA00438; Wed, 3 Jan 1996 09:25:51 -0800 (PST) Message-Id: <199601031725.JAA00438@corbin.Root.COM> To: gpalmer@westhill.cdrom.com cc: dfr@render.com, hackers@freebsd.org Subject: Re: 2.1 panic: panic: nfsreq nogrps In-reply-to: Your message of "Wed, 03 Jan 96 04:26:22 PST." <10191.820671982@westhill.cdrom.com> From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 03 Jan 1996 09:25:50 -0800 Sender: owner-hackers@freebsd.org Precedence: bulk >David Greenman wrote in message ID ><199601030538.VAA00222@corbin.Root.COM>: >> >in the origional mail), and I was just looking at the program which >> >was running at the time, and it does nothing more complicated than > >> The setgroups() can happen at any time and doesn't in itself cause a panic. >> The panic message "nfsreq nogrps" indicates that an I/O operation is being >> attempted on behalf of a process that has no groups in it's group list. This >> isn't a valid state as group[0] is always the effective gid. If the process >> didn't get this way because of setgroups(), then it's happening somewhere >> else in the kernel. I suppose one work-around kludge might be to substitute >> the "nobody" group (-2) for processes that otherwise belong to no groups. > >Look likes we'll need to do that as with a freshly updated copy of the >sources it just suffered the same panic again. Any idea why this is all-of-a-sudden happening regularly? -DG