On Wed, 2003-01-08 at 09:00, [EMAIL PROTECTED] wrote: > On Mon, Jan 06, 2003 at 09:35:35AM +0100, Volker Lendecke wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > Modified Files: > > > Tag: SAMBA_3_0 > > > close.c dir.c open.c > > > Log Message: > > > Fix problem with "hide unreadable". stat file opens are baaack :-). > > > > Do you have a two-liner with an explanation? I'd like to know what to > > look for. > > In the oplock break state an open was being done (in the check is user can > read file code) that caused a recursion (ie. another oplock break request > going to the same smbd). That was a bad thing :-). Hence, the return of > stat opens which won't cause an oplock break but still allow ACLs to be > read.
So what happens with kernel oplocks here? Won't they trigger? And if we are going to do the open anyway, why don't we just use the result of that - why do we need to check the ACL? Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
signature.asc
Description: This is a digitally signed message part
