From owner-freebsd-current Sun Nov 26 15:43:00 1995 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA12761 for current-outgoing; Sun, 26 Nov 1995 15:43:00 -0800 Received: from cyb (cyb.alaska.net [204.17.139.166]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id PAA12747 for ; Sun, 26 Nov 1995 15:42:51 -0800 Received: by cyb (Smail3.1.29.1 #9) id m0tJqeY-0006edC; Sun, 26 Nov 95 14:38 AKST Message-Id: From: loodvrij@gridpoint.com (Bruce J. Keeler) Subject: No groups? To: current@freebsd.org Date: Sun, 26 Nov 1995 14:38:34 -0900 (AKST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 771 Sender: owner-current@freebsd.org Precedence: bulk I've just tracked down a panic if anyone is interested. The panic arose while attemping to use smail with the configuration directory /usr/local/lib/smail shared via nfs. The problem is that smail calls setgroups() thusly: /* clear out all extra groups. We don't want to have to deal with them */ { gid_t dummy; (void) setgroups(0, &dummy); } setgroups() duly sets the process's cr_ngroups to 0. This causes a panic later in nfs_request(). It seems unreasonable to me that setgroups() should allow this. It checks for the first arg being > NGROUPS, perhaps it should also check for <= 1. -- Bruce J. Keeler Internet: bruce@gridpoint.com -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-