From owner-freebsd-threads@FreeBSD.ORG  Fri Apr 11 00:49:02 2003
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
Delivered-To: freebsd-threads@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0ABE437B401
	for <freebsd-threads@freebsd.org>;
	Fri, 11 Apr 2003 00:49:02 -0700 (PDT)
Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 40EC043FA3
	for <freebsd-threads@freebsd.org>;
	Fri, 11 Apr 2003 00:49:01 -0700 (PDT)
	(envelope-from jroberson@chesapeake.net)
Received: from localhost (jroberson@localhost)
	by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h3B7n0l55915
	for <freebsd-threads@freebsd.org>;
	Fri, 11 Apr 2003 03:49:00 -0400 (EDT)
	(envelope-from jroberson@chesapeake.net)
Date: Fri, 11 Apr 2003 03:49:00 -0400 (EDT)
From: Jeff Roberson <jroberson@chesapeake.net>
To: freebsd-threads@freebsd.org
Message-ID: <20030411034715.T37530-100000@mail.chesapeake.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: KSE signals broken by 1:1 commit.
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2003 07:49:02 -0000

So I don't think you are fair enough!
I ever posted a message said that jeff's patch had bug,
the bug is signal lost, but he obviously didn't fixed it,
and you guy allowed him to commit it, please search arch list
about 1:1 thread! I don't think delaying some days of libthr
change to kernel would hurt anything, I had reported
the problem and why did core still allow him to commit?

David Xu


The problem is a minor race where an exiting thread could have a process
wide signal pending when it exits.  Hardly a critical issue.  Why did we
allow any of kern_thread.c to be commited when it obviously doesn't work
at all?

Cheers,
Jeff