Date: Sat, 10 Dec 2011 01:20:09 GMT From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/163076: It is not possible to read in chunks from linprocfs and procfs. Message-ID: <201112100120.pBA1K91a092473@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: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Jaakko Heinonen <jh@FreeBSD.org> 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: Sat, 10 Dec 2011 02:13:56 +0100 Jaakko Heinonen <jh@FreeBSD.org> writes: > Dag-Erling Sm=C3=B8rgrav wrote: > > 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. A fixed-length sbuf may overflow intentionally (as in pseudofs) or unintentionally; a dynamic sbuf may also overflow due to a memory allocation failure. The first two cases are expected, but the third is not, and I am not sure the sbuf should be considered valid in such a case. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201112100120.pBA1K91a092473>