From owner-cvs-all Mon Sep 30 18: 8:39 2002 Delivered-To: cvs-all@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 36D7237B401; Mon, 30 Sep 2002 18:08:38 -0700 (PDT) Received: from dragon.nuxi.com (trang.nuxi.com [66.92.13.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8749C43E65; Mon, 30 Sep 2002 18:08:37 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (obrien@localhost [127.0.0.1]) by dragon.nuxi.com (8.12.6/8.12.2) with ESMTP id g9118bq2082192; Mon, 30 Sep 2002 18:08:37 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.12.6/8.12.5/Submit) id g9118b3b082191; Mon, 30 Sep 2002 18:08:37 -0700 (PDT) Date: Mon, 30 Sep 2002 18:08:37 -0700 From: "David O'Brien" To: Juli Mallett Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/alpha/osf1 osf1_signal.c src/sys/compat/linprocfs linprocfs.c src/sys/compat/linux linux_misc.c linux_signal.c src/sys/compat/svr4 svr4_filio.c svr4_signal.c src/sys/conf files src/sys/fs/procfs procfs_ctl.c src/sys/kern init_main.c ... Message-ID: <20021001010837.GB61347@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org Mail-Followup-To: David O'Brien , Juli Mallett , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org References: <200210010007.g9107Tkb058991@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200210010007.g9107Tkb058991@freefall.freebsd.org> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 5.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Sep 30, 2002 at 05:07:29PM -0700, Juli Mallett wrote: > jmallett 2002/09/30 17:07:28 PDT > > Modified files: > sys/alpha/osf1 osf1_signal.c > sys/compat/linprocfs linprocfs.c > sys/compat/linux linux_misc.c linux_signal.c > sys/compat/svr4 svr4_filio.c svr4_signal.c > sys/conf files > sys/fs/procfs procfs_ctl.c > sys/kern init_main.c kern_exit.c kern_fork.c > kern_kthread.c kern_proc.c kern_sig.c > subr_trap.c tty.c subr_sigq.c > sys/sys ksiginfo.h proc.h > Log: > (Forced commit, to clarify previous commit of ksiginfo/signal queue code.) > > I've added a structure, kernel-private, to represent a pending or in-delivery > signal, called `ksiginfo'. It is roughly analogous to the basic information > that is exported by the POSIX interface 'siginfo_t', but more basic. I've > added functions to allocate these structures, and further to wrap all signal > operations using them. I think you broke world with this commit. But that aside, what does this gain us? Where was it discussed that this was a good direction to go in? I don't recall seeing it on arch@. I don't recall a patch being posted to arch@. We *just* had a thread about the need to stabilize 5-CURRENT, and now we have a commit to very low-level infrastructure. This has the potential to FUBAR signals all over again. AND now we aren't going to know if its KSE or juli-signals that is the cause. Is there really sufficient time to get these changes panned out and stabilized by 5.0-RELEASE? Perhaps they should live in a perforce branch for a while. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message