From owner-freebsd-current Mon Aug 12 12: 9:25 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E903C37B400 for ; Mon, 12 Aug 2002 12:09:22 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id DE32943E3B for ; Mon, 12 Aug 2002 12:09:21 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id FAA09988; Tue, 13 Aug 2002 05:09:05 +1000 Date: Tue, 13 Aug 2002 05:14:07 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: "Andrey A. Chernov" Cc: Terry Lambert , David Xu , Julian Elischer , FreeBSD CURRENT Subject: Re: cvs commit: src/sys/kern kern_sig.c (fwd) In-Reply-To: <20020812172131.GA2139@nagual.pp.ru> Message-ID: <20020813050607.R25861-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, 12 Aug 2002, Andrey A. Chernov wrote: > On Tue, Aug 13, 2002 at 03:15:02 +1000, Bruce Evans wrote: > > > > Anyway, it has one blatant style bug (not 1TBS) and no explanation of > > the bug, so it should not have been committed verbatim. See another > > reply for an analysis of the patch. > > According to commit guide, explanations are not commited, only what is > changed. For explanation (terminal group mismatch) read whole thread, > especially David's analysis. The analysis in the thread seems to be incomplete. > What another reply you mean? I just wrote one :-). Rereading earlier analysis just gave me a hint about tcsetpgrp() to the same value causes problems: it causes an unexpected SIGTTOU because a background process attemps to do something (TIOCSPGRP) that can only be done in the foreground (the background process is forced to wait until it gets to the foreground, and it doesn't help for the change to be null since the process must be in the foreground to even check for null changes). Presumably the child su is in the foreground at that point. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message