From owner-freebsd-threads@FreeBSD.ORG  Thu Apr 24 20:16:50 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 A287C37B401
	for <freebsd-threads@freebsd.org>;
	Thu, 24 Apr 2003 20:16:50 -0700 (PDT)
Received: from smtp01.syd.iprimus.net.au (smtp01.syd.iprimus.net.au
	[210.50.30.52])	by mx1.FreeBSD.org (Postfix) with ESMTP id 2A6A743FE1
	for <freebsd-threads@freebsd.org>;
	Thu, 24 Apr 2003 20:16:50 -0700 (PDT)
	(envelope-from tim@robbins.dropbear.id.au)
Received: from dilbert.robbins.dropbear.id.au (210.50.218.164) by
	smtp01.syd.iprimus.net.au (7.0.012)
	id 3E96D1D200222E64 for freebsd-threads@freebsd.org;
	Fri, 25 Apr 2003 13:16:48 +1000
Received: by dilbert.robbins.dropbear.id.au (Postfix, from userid 1000)
	id 8EE7FC90D; Fri, 25 Apr 2003 13:16:56 +1000 (EST)
Date: Fri, 25 Apr 2003 13:16:56 +1000
From: Tim Robbins <tjr@FreeBSD.ORG>
To: freebsd-threads@freebsd.org
Message-ID: <20030425131656.A93380@dilbert.robbins.dropbear.id.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Subject: Threading and credential changes
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, 25 Apr 2003 03:16:50 -0000

I'm trying to understand the way a thread's td_ucred is updated. In ast(),
cred_update_thread() is called to update it when it doesn't match the one
stored in the proc. However, setuid() etc. don't set the TDF_ASTPENDING flag
on any threads, not even the current thread. Am I misunderstanding what ast()
does, does the thread's cred get updated in some other way, or is this a bug?


Tim