trans2 response handling

[Murali Bashyam]

Stefan

To fix the issue, could we do something like not serialize when we are
handling trans2 request/responses i.e turn off the serialise flag just
before and during the whole exchange, and turn it on after the exchange?
Would this work?

Murali

On 7/31/06, Murali Bashyam <mbcoder at gmail.com> wrote:
>
>
>
> On 7/30/06, Stefan (metze) Metzmacher <metze at samba.org> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Hi Murali,
> >
> > > is serializing the next response waiting for the smb client raw layer
> > to
> > > indicate to the packet layer somehow that it's finished with the
> > previous
> > > response. Is this a known issue with the tp2 snapshot?
> >
> > we haven't noticed this yet...
> >
> > > I don't see any change to fix this problem in these code segments in
> > the
> > > latest version of samba 4, and was wondering whether anyone else has
> > > observed this.
> >
> > Do you have some code that demonstrates this, then it would be easier
> > for us to fix it...
>
>
> By this, do u mean test code  which exercises multiple  trans2 responses?
> This problem can be found by simply using windows explorer on a large
> directory, through the vfs cifs layer.
>
> Or did u want me to include relevant samba4 code segments which point to
> the problem?
>
> Murali
>
> thanks for the report!
> >
> > metze
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.2 (GNU/Linux)
> > Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
> >
> > iD8DBQFEzaFAm70gjA5TCD8RAif0AJ0VB2Ce/VFUxpLv/F40y/Ns0Nln8wCgjmbR
> > DpaBPMkfDe8yT9iS8HGd6MA=
> > =KQCn
> > -----END PGP SIGNATURE-----
> >
>
>