On 01/20/10 13:06, Florian Manschwetus wrote:
Am 20.01.2010 20:50, schrieb Afshin Salek:
Florian Manschwetus wrote:
Am 19.01.2010 19:52, schrieb Afshin Salek:
We should first determine what the nature of the problem is
and then start the diagnosis process. I don't see any clear
problem description in the bugzilla.
What operation is being performed when this crash happens?
I can see that the crash has been fixed, so you are saying
there is still a problem and you think it's a server side
issue?
You haven't responded to this question, so do you have the
smbclient fix for the crash and you still see a problem or
you don't have the fix?
Afshin
I have the fix and it was released yesterday for samba stable (3.4.5),
but it would need about six month until it would make it in the
mainstream binary distributions, so we would need the server to be fixed
asap. (possible impact also on opensolaris and macos)
AFAIA, the server-side doesn't need to be fixed. The Samba code
was using the wrong field in the MSRPC response.
smbclient may have gotten away with a small number of shares on
Windows but it could have run into a similar problem with a large
number of shares - enough shares to exceed the limit for a single
request.
The idea was to get a dtrace hack, that fixes the affected replies.
If it is possible to do so.
You may create such a hack for yourself but I don't think we should
be distributing something like that - particularly when the real
fix is already being distributed by others.
Alan
_______________________________________________
cifs-discuss mailing list
cifs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss
