Date: Tue, 22 Mar 2016 21:46:27 -0500 From: Benjamin Kaduk <bjkfbsd@gmail.com> To: Bryan Drewery <bdrewery@freebsd.org> Cc: "cem@FreeBSD.org" <cem@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "src-committers@freebsd.org" <src-committers@freebsd.org> Subject: Re: svn commit: r297201 - in head: share/man/man4 sys/dev/filemon Message-ID: <CAJ5_RoD1J_LOvN5hzSF_DsUHd_mtn=XZDYcZU5xOBiyRSVjVDg@mail.gmail.com> In-Reply-To: <D2476F6F-8C58-489D-9654-DFF2AEB9941F@FreeBSD.org> References: <201603222241.u2MMf7ub090070@repo.freebsd.org> <CAG6CVpUxC6Nov7ocy5eEpcQFLd%2BQdXUxZWs49kTesWZo_VqncQ@mail.gmail.com> <D2476F6F-8C58-489D-9654-DFF2AEB9941F@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 22, 2016 at 9:11 PM, Bryan Drewery <bdrewery@freebsd.org> wrote: > > > > The manpage for close(2) does document some errors, one being ENOSPC. The > close(2) behavior of returning write(2), really VOP_WRITE(9), errors though > is specific to filemon since all of the writes are hidden and this is the > only place to return an error. I have a review open to resolve a similar > issue in alq(9) as well since all of the writes are asynchronous and > there's no API to retrieve any error from. > filemon is not unique in this regard; the AFS filesystem buffers writes locally and in some cases errors writing to the remote server can be delayed until close(). Of course, very few softwares actually check the return value of close, so this can cause trouble sometimes... -Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ5_RoD1J_LOvN5hzSF_DsUHd_mtn=XZDYcZU5xOBiyRSVjVDg>