Date: Mon, 14 May 2007 09:45:40 -0300 From: "Marc G. Fournier" <freebsd@hub.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: stable@FreeBSD.org Subject: Re: UNIX domain sockets MFC's Message-ID: <CCCB15AE824E5AFDAA3651A9@ganymede.hub.org>
next in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Monday, May 14, 2007 11:29:12 +0100 Robert Watson <rwatson@FreeBSD.org> wrote: > > On Sat, 12 May 2007, Marc G. Fournier wrote: > >>> The fix for this has now been merged as 1.155.2.22. As there have been no >>> new reports of UNIX domain socket problems in the last couple of days, it >>> sounds like the MFC of the last batch of fixes and cleanups has not lead to >>> problems. >> >> I've just upgraded my kernel to the latest, to include the MFC'd code above >> ... > > Yes -- I was very specific in my e-mail regarding the MFC's that they were > not believed to address the problem you are reporting. I think we have a > leak in the way some edge case is handled with regard to UNIX domain socket > shutdown. What would be really nice to know is if that persists in 7-CURRENT, > in which we've redone the way the socket life cycle works. However, I don't > know if you are able to tolerate booting a 7-CURRENT kernel in your > environment...? On that server, that could be very difficult ... if this was happening on any of my HP servers, I would in a minute ... > Did we determine whether backing out to before the unpcb socket reference > count change made any difference for you? The problem appeared to persist after backing it out ... I'm curious about something ... way back, when I was using unionfs, I had a major problem with vnode leakage ... as I mentioned before, this server is the only one I have that uses geom/gmirror on its drives, the rest all use hardware RAID ... is there *any* possibility that I'm seeing some sort of interaction issue? It really bothers me that the only server that I'm seeing this one is the one that I'm using software RAID on ... Would it be useful to add some DEBUG statements to the socket code, to trace open/close/flush/etc? Maybe to see where flush's are being started, but never completed? That sort of thing? - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGSFn14QvfyHIvDvMRAow2AKC67Y0QuiiF+ZJA5Tpbd3WUvcmdTwCaAgZS OY4em31JQzIIbs1CUcmpHNo= =1Mqr -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CCCB15AE824E5AFDAA3651A9>