From owner-freebsd-hackers  Wed Jan  3 04:26:47 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id EAA03317
          for hackers-outgoing; Wed, 3 Jan 1996 04:26:47 -0800 (PST)
Received: from westhill.cdrom.com (westhill.cdrom.com [192.216.223.138])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA03310
          for <hackers@freebsd.org>; Wed, 3 Jan 1996 04:26:42 -0800 (PST)
From: gpalmer@westhill.cdrom.com
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by westhill.cdrom.com (8.6.12/8.6.12) with SMTP id EAA10193
          ; Wed, 3 Jan 1996 04:26:23 -0800
X-Authentication-Warning: westhill.cdrom.com: Host localhost.cdrom.com didn't use HELO protocol
To: davidg@Root.COM
cc: dfr@render.com, hackers@freebsd.org
Subject: Re: 2.1 panic: panic: nfsreq nogrps 
In-reply-to: Your message of "Tue, 02 Jan 1996 21:38:13 PST."
             <199601030538.VAA00222@corbin.Root.COM> 
Date: Wed, 03 Jan 1996 04:26:22 -0800
Message-ID: <10191.820671982@westhill.cdrom.com>
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.

Gary