From owner-cvs-src@FreeBSD.ORG Wed Nov 9 08:07:11 2005 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E25B716A41F; Wed, 9 Nov 2005 08:07:11 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9377643D46; Wed, 9 Nov 2005 08:07:11 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.0.250] (ppp-71-139-0-107.dsl.snfc21.pacbell.net [71.139.0.107]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id jA9877DI017313 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 9 Nov 2005 00:07:08 -0800 Message-ID: <4371AE25.3090008@root.org> Date: Wed, 09 Nov 2005 00:07:01 -0800 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <26185.1131519693@critter.freebsd.dk> In-Reply-To: <26185.1131519693@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Craig Rodrigues , cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern vfs_mount.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Nov 2005 08:07:12 -0000 Poul-Henning Kamp wrote: > In message <43716BD6.5050604@root.org>, Nate Lawson writes: > > >>While I don't have ideas for a better general mechanism for this, I >>think it sets a bad precedent. We can't have every complex syscall >>transporting its own error message strings back to the user program. >>And we can't expand errno to be the union of every single API-specific >>error either. > > > That was one the main points of my ioctl talk at BSDcan. > > One way to solve it: > > Hang a sbuf pointer in each thread and APIs cound stuff their error > message there. > > Add a new syscall to return the string to userland. > > Modify perror(3), err(3) and similar to pull out the "extended" > error, if there is one. This sounds better. Not sure if it's fully baked, but definitely a better direction. -- Nate