Jeremy Allison writes:
As there are more people who seem to have this problem I've opened a
bugzilla report: https://bugzilla.samba.org/show_bug.cgi?id=3962
This is a Windows client bug I believe. There's a hotfix for it I think...
Jerry knows more of the details. I'll try and find it.
The hotfix that has been mentioned is this one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;329234
It states that the problem is fixed with version 5.1.2600.1130 of
Win32spl.dll and that it has been fixed in SP2, yet I see the problem with
an XPSP2 and version 5.1.2600.2180 of win32spl.dll.
I don't have any knowledge of samba internals, but it seems to me that
repeated access to what seems to be the same set of calls should not lead to
unlimited memory consumption. A broken client should not be able to
break samba, should it?
If this really is a case where it can't be prevented that incorrect
behaviour of a client leads to problems at the samba side, could you please
explain why this is so (if you have time, of course)?
Regards,
roel
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
