From owner-cvs-all Mon Nov 9 07:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13872 for cvs-all-outgoing; Mon, 9 Nov 1998 07:08:04 -0800 (PST) (envelope-from owner-cvs-all@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13864; Mon, 9 Nov 1998 07:08:02 -0800 (PST) (envelope-from truckman@FreeBSD.org) From: Don Lewis Received: (from truckman@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id HAA11552; Mon, 9 Nov 1998 07:08:05 -0800 (PST) Date: Mon, 9 Nov 1998 07:08:05 -0800 (PST) Message-Id: <199811091508.HAA11552@freefall.freebsd.org> To: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: cvs commit: src/sys/kern kern_fork.c kern_proc.c kern_prot.c src/sys/sys proc.h Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk truckman 1998/11/09 07:08:04 PST Modified files: sys/kern kern_fork.c kern_proc.c kern_prot.c sys/sys proc.h Log: If the session leader dies, s_leader is set to NULL and getsid() may dereference a NULL pointer, causing a panic. Instead of following s_leader to find the session id, store it in the session structure. Jukka found the following info: BTW - I just found what I have been looking for. Std 1003.1 Part 1: SYSTEM API [C LANGUAGE] section 2.2.2.80 states quite explicitly... Session lifetime: The period between when a session is created and the end of lifetime of all the process groups that remain as members of the session. So, this quite clearly tells that while there is any single process in any process group which is a member of the session, the session remains as an independent entity. Reviewed by: peter Submitted by: "Jukka A. Ukkonen" Revision Changes Path 1.52 +6 -2 src/sys/kern/kern_fork.c 1.38 +2 -1 src/sys/kern/kern_proc.c 1.41 +2 -2 src/sys/kern/kern_prot.c 1.59 +2 -1 src/sys/sys/proc.h To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message