Date: Fri, 9 Dec 2011 14:40:09 GMT From: Jaakko Heinonen <jh@FreeBSD.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/163076: It is not possible to read in chunks from linprocfs and procfs. Message-ID: <201112091440.pB9Ee9gU003283@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/163076; it has been noted by GNATS. From: Jaakko Heinonen <jh@FreeBSD.org> To: Dag-Erling =?utf-8?B?U23DuHJncmF2?= <des@des.no> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, Petr Salinger <Petr.Salinger@seznam.cz>, bug-followup@FreeBSD.org, mdf@FreeBSD.org Subject: Re: kern/163076: It is not possible to read in chunks from linprocfs and procfs. Date: Fri, 9 Dec 2011 16:35:30 +0200 On 2011-12-09, Dag-Erling Smørgrav wrote: > Jaakko Heinonen <jh@FreeBSD.org> writes: > > As I wrote existing code depends on sbuf_len() to return the actual > > length regardless of the error status after sbuf_finish(). I am not > > willing to through all code using sbufs to check where it causes > > problems. phk@ asserts that r222004 is correct. > > What if the sbuf is in a state where asking for its length is > meaningless? Could you give an example about such state? Isn't the length first initialized to zero and then increased only when byte(s) has been successfully appended to the buffer? sbuf_len() has worked for unfinished buffers since r71724. -- Jaakko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112091440.pB9Ee9gU003283>