Date: Thu, 19 Jun 2003 23:12:08 +0400 From: Dmitry Sivachenko <demon@freebsd.org> To: John-Mark Gurney <gurney_j@efn.org> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern kern_descrip.c Message-ID: <20030619191208.GA97562@fling-wing.demos.su> In-Reply-To: <20030619182213.GB64061@funkthat.com> References: <200306181857.h5IIvwfY075070@repoman.freebsd.org> <20030619082713.GC79448@HAL9000.homeunix.com> <20030619115532.A629@odysseus.silby.com> <20030619150711.GA56423@fling-wing.demos.su> <20030619140309.H629@odysseus.silby.com> <20030619182213.GB64061@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 19, 2003 at 11:22:13AM -0700, John-Mark Gurney wrote: > Mike Silbersack wrote this message on Thu, Jun 19, 2003 at 14:03 -0500: > > > > On Thu, 19 Jun 2003, Dmitry Sivachenko wrote: > > > > > > Oh, btw; while running my fd hog program as root, cron decided to core. > > > > Someone should take a look at it and figure out where it doesn't check the > > > > return value of something which allocates a fd (or socket?) > > > > > > > > > > bin/49096 ? > > > > That looks like it might be it, I'll give it a try and commit it if solves > > the problem for me. > > Actually, that patch should be committed even if it doesn't solve the > problem. The if (in == NULL) is useless since we already tried to > read a char from it. > I tested it before submitting trying to reproduce symptoms desctibed in the PR. This patch solved the problem for me. FYI.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030619191208.GA97562>