Re: named pipes memory leak?

2003-11-15 Thread Don Lewis
On 11 Nov, Lukas Ertl wrote: > On Tue, 11 Nov 2003, Lukas Ertl wrote: > >> Unfortunately, we are still seeing a problem here: we are running uvscan >> (virus scanner), and while running it we are still seeing increasing unpcb >> usage and orphaned unix domain sockets. >> >> We added some debug pri

Re: named pipes memory leak?

2003-11-11 Thread Lukas Ertl
On Tue, 11 Nov 2003, Don Lewis wrote: > Now that I've had some time to think about it, if you reuse the same > fifo, you'll run into the same problem that caused me to abandon my > previous fifo_inactive() version of the cleanup code, which is stale > data being left in the fifo after both ends ha

Re: named pipes memory leak?

2003-11-11 Thread Don Lewis
On 11 Nov, Don Lewis wrote: > On 11 Nov, Lukas Ertl wrote: >> Sorry, I probably missed an important part: we're creating the FIFOs on >> nullfs mounts - the test script works great on plain UFS mounts, but the >> null layer seems to VREF the vnode once again, so v_usecount is 2, thus it >> is miss

Re: named pipes memory leak?

2003-11-11 Thread Don Lewis
On 11 Nov, Lukas Ertl wrote: > On Tue, 11 Nov 2003, Lukas Ertl wrote: > >> Unfortunately, we are still seeing a problem here: we are running uvscan >> (virus scanner), and while running it we are still seeing increasing unpcb >> usage and orphaned unix domain sockets. >> >> We added some debug pri

Re: named pipes memory leak?

2003-11-11 Thread Lukas Ertl
On Tue, 11 Nov 2003, Lukas Ertl wrote: > Unfortunately, we are still seeing a problem here: we are running uvscan > (virus scanner), and while running it we are still seeing increasing unpcb > usage and orphaned unix domain sockets. > > We added some debug printfs to the fifo routines and found ou

Re: named pipes memory leak?

2003-11-11 Thread Lukas Ertl
On Mon, 10 Nov 2003, Don Lewis wrote: > On 10 Nov, Lukas Ertl wrote: > > On Mon, 10 Nov 2003, Don Lewis wrote: > >> > >> If fifo_open() is interrupted, fifo_close() never gets called, and the > >> resources are not recovered. I wish doing the resource recovery in > >> fifo_inactive() would have w

Re: named pipes memory leak?

2003-11-10 Thread Don Lewis
On 10 Nov, Lukas Ertl wrote: > On Mon, 10 Nov 2003, Don Lewis wrote: > >> On 10 Nov, Lukas Ertl wrote: >> > >> > The following shell script freezes a machine in several minutes and needs >> > a power cycle. You can see the increasing memory in vmstat -z (unpcb) and >> > netstat -u. The kernel is

Re: named pipes memory leak?

2003-11-10 Thread Lukas Ertl
On Mon, 10 Nov 2003, Don Lewis wrote: > On 10 Nov, Lukas Ertl wrote: > > > > The following shell script freezes a machine in several minutes and needs > > a power cycle. You can see the increasing memory in vmstat -z (unpcb) and > > netstat -u. The kernel is FreeBSD 5.1-CURRENT Tue Nov 4 14:08:2

Re: named pipes memory leak?

2003-11-10 Thread Don Lewis
On 10 Nov, Lukas Ertl wrote: > Hi, > > is there a known problem with named pipes in -CURRENT? > > The following shell script freezes a machine in several minutes and needs > a power cycle. You can see the increasing memory in vmstat -z (unpcb) and > netstat -u. The kernel is FreeBSD 5.1-CURRENT

named pipes memory leak?

2003-11-10 Thread Lukas Ertl
Hi, is there a known problem with named pipes in -CURRENT? The following shell script freezes a machine in several minutes and needs a power cycle. You can see the increasing memory in vmstat -z (unpcb) and netstat -u. The kernel is FreeBSD 5.1-CURRENT Tue Nov 4 14:08:23 CET 2003. ---8<--- #/b