From owner-freebsd-arch Sun Sep 3 5: 4:47 2000 Delivered-To: freebsd-arch@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id E1B6537B424 for ; Sun, 3 Sep 2000 05:04:42 -0700 (PDT) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id FAA24681 for ; Sun, 3 Sep 2000 05:04:42 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id FAA09774 for ; Sun, 3 Sep 2000 05:04:41 -0700 (PDT) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id FAA19222 for arch@freebsd.org; Sun, 3 Sep 2000 05:04:41 -0700 (PDT) Date: Sun, 3 Sep 2000 05:04:41 -0700 (PDT) From: Don Lewis Message-Id: <200009031204.FAA19222@salsa.gv.tsc.tdk.com> To: arch@freebsd.org Subject: width of cr_ref Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that sockets hold a reference to the ucred structure, should cr_ref be a wider type? Really busy servers with a lot of sockets owned by one user might overflow cr_ref, causing mysterious crashes when the ucred structure is freed too early. struct ucred { u_short cr_ref; /* reference count */ uid_t cr_uid; /* effective user id */ short cr_ngroups; /* number of groups */ gid_t cr_groups[NGROUPS]; /* groups */ }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message