From owner-cvs-src@FreeBSD.ORG  Wed Nov 12 14:52:36 2003
Return-Path: <owner-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 30D3516A4CE; Wed, 12 Nov 2003 14:52:36 -0800 (PST)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6069F43FD7; Wed, 12 Nov 2003 14:52:32 -0800 (PST)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.10/8.12.10) with ESMTP id hACMqNNZ000689;
	Wed, 12 Nov 2003 23:52:24 +0100 (CET)
	(envelope-from phk@phk.freebsd.dk)
To: Kirk McKusick <mckusick@beastie.mckusick.com>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Wed, 12 Nov 2003 14:19:58 PST."
             <200311122219.hACMJwaG007327@beastie.mckusick.com> 
Date: Wed, 12 Nov 2003 23:52:23 +0100
Message-ID: <688.1068677543@critter.freebsd.dk>
cc: "Brian F. Feldman" <green@FreeBSD.org>
cc: src-committers@FreeBSD.org
cc: Scott Long <scottl@FreeBSD.org>
cc: cvs-all@FreeBSD.org
cc: cvs-src@FreeBSD.org
Subject: Re: cvs commit: src/bin/df df.c src/sys/kern syscalls.master
	vfs_bio.c vfs_cluster.c vfs_syscalls.c src/sys/sys mount.h
	src/sys/ufs/ffs ffs_vfsops.c 
X-BeenThere: cvs-src@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the src tree <cvs-src.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-src>
List-Post: <mailto:cvs-src@freebsd.org>
List-Help: <mailto:cvs-src-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-src>,
	<mailto:cvs-src-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Nov 2003 22:52:36 -0000

In message <200311122219.hACMJwaG007327@beastie.mckusick.com>, Kirk McKusick wr
ites:
>	From: "Brian F. Feldman" <green@FreeBSD.org>
>	Date: Wed, 12 Nov 2003 14:16:07 -0500
>	Sender: owner-src-committers@FreeBSD.org
>	X-Loop: FreeBSD.ORG
>
>	Does this mean someone may be free to write wrappers that block
>	ENOSYS, execute statfs calls, and fall back to ostatfs calls
>	(translating 64->32 bit values as best as possible, like the kernel
>	does) returning the new statfs?  Obviously, this would just be to
>	add a safety window for the transition period and to be removed
>	before a -RELEASE.
>
>	-- 
>	Brian Fundakowski Feldman                   \'[ FreeBSD ]''''''''''\
>	  <> green@FreeBSD.org                       \  The Power to Serve! \
>	 Opinions expressed are my own.               \,,,,,,,,,,,,,,,,,,,,,,\
>
>The above would certainly be possible. If this were a more heavily
>used interface (like say stat), it would be a useful exercise. But
>I do not feel it is really necessary for statfs. However, I am not
>going to object if someone wants to go through the exercise of 
>implementing your suggestion.

Uhm, as far as I recall, calling an undefined system call gives you
a signal you need to handle, before you will ever see the ENOSYS.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.