summaryrefslogtreecommitdiff
path: root/pcp
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2004-09-19 01:16:45 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 10:52:42 -0500
commitf820b921cdeba93f21237e32f9872340d3afc347 (patch)
treeb1d28ce13b9b185a3be657790a84a1ee7c4cecd2 /pcp
parent7418d20abe0870745f4845de59aa92128ea646ef (diff)
downloadsamba-f820b921cdeba93f21237e32f9872340d3afc347.tar.gz
samba-f820b921cdeba93f21237e32f9872340d3afc347.tar.bz2
samba-f820b921cdeba93f21237e32f9872340d3afc347.zip
r2413: Arggg. Stupid, stupid, stupid me ! I added a paranoia test
case when I was developing the deferred open case and made it too tight. It will fire (incorrectly) and panic when a client does a second open for a file with a different mid (multiplex-id) request. Doh ! This is a perfectly valid thing for a client to do (have two pending opens with different mids outstanding on the same file) and currently when the first pending open expires with a share violation the paranoia code will panic smbd. It's a rare condition, but obvious now I've looked at the code. Fix for bug #1743. Jeremy. (This used to be commit e1bf108ae965ae730c67524164fa36497ea905b5)
Diffstat (limited to 'pcp')
0 files changed, 0 insertions, 0 deletions