From owner-freebsd-bugs Wed Nov 15 03:39:26 1995 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA21880 for bugs-outgoing; Wed, 15 Nov 1995 03:39:26 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.17]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA21871 for ; Wed, 15 Nov 1995 03:39:21 -0800 Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id DAA03033; Wed, 15 Nov 1995 03:39:17 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id DAA00558; Wed, 15 Nov 1995 03:38:49 -0800 Message-Id: <199511151138.DAA00558@corbin.Root.COM> To: jan@todonix.ping.de (Jan Wedekind) cc: freebsd-bugs@freebsd.org Subject: Re: panic: nfsreq nogrps In-reply-to: Your message of "Wed, 15 Nov 95 12:23:55 +0100." From: David Greenman Reply-To: davidg@Root.COM Date: Wed, 15 Nov 1995 03:38:48 -0800 Sender: owner-bugs@freebsd.org Precedence: bulk >any idea where the above panic can result from ? > (located at nfs/nfs_socket.c line 920) > >the machine (running 2.0.5 RELASE with kernel from 2.1.0-1104-SNAP) >only mounts some directories from an 1.1.5 machine. It's usually caused by Smail. Smail does a setgroups(0,foo) which isn't valid (you have to have at least one group in the list - the effective gid). This was fixed recently in the version of Smail in the ports tree. The bug in the kernel was fixed in -current just recently. The kernel fix is to disallow ngroups=0. -DG