Date: Thu, 08 Jul 2004 12:07:56 +0900 (JST) From: KOIE Hidetaka (=?iso-2022-jp?B?GyRCOHE5PjFRTjQhdz90TX01OzgmGyhC?=) <koie@suri.co.jp> To: bde@zeta.org.au Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/68690: write(2) returns wrong vlalue when EFAULT Message-ID: <20040708.120756.104051089.koie@suri.co.jp> In-Reply-To: <20040707172014.C3185@gamplex.bde.org> References: <200407051221.i65CLC3Q057710@www.freebsd.org> <20040707172014.C3185@gamplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks for your inspection. Message-Id: <20040707172014.C3185@gamplex.bde.org> Date: Wed, 7 Jul 2004 18:23:57 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> Subject: Re: kern/68690: write(2) returns wrong vlalue when EFAUL.. | Do you actually see the file pointer advanced? This may be file system | dependent. ffs is supposed to back out of the write, and it does so | for me. Output: | | %%% | pos=0 | write(20480)->-1 (should be 12288) | write: Bad address | pos=0 (should be 12288) | %%% I was unaware of examining on NFS. %%% pos=0 write(20480)->-1 (should be 12288) write: Bad address pos=8192 (should be 12288) %%% The file pointer is not backed. | > >Fix: I understand some problems exist. -- KOIE Hidetaka / koie@suri.co.jp / SURIGIKEN Co.,LTD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040708.120756.104051089.koie>