smbd panic at find_oplock_types().

[Volker Lendecke]

On Tue, Aug 05, 2014 at 11:22:19AM -0700, Hemanth Thummala wrote:
> Volker,
> These are user files not internal/temp files. Yeah stat open checks for
> non-zero access mask. But I have seen at one place where we send zero
> access mask along NO_OPLOCK flag.
> 
> In create_file_unixpath():
> ...
> /* Open the base file. */
> status = create_file_unixpath(conn, NULL, smb_fname_base, 0==> Access mask,
>       FILE_SHARE_READ
>       | FILE_SHARE_WRITE
>       | FILE_SHARE_DELETE,
>       base_create_disposition,
>       0, 0, 0==> oplock, 0, 0, NULL, NULL,
>       &base_fsp, NULL);
> TALLOC_FREE(smb_fname_base);
> ...
> 
> But this will happen only when the request comes for stream files. But I
> feel we should mark access mask non-zero so that we can filter these shared
> mode locks with is_stat_open().
> In my case, file doesn't have any streams. So I am ruling this possibility
> out. But thought of showing that we have a case where we are using zero
> access mask for stat/internal opens.

The problem is -- access_mask==0 should have broken the
oplock. I don't really see how this could not happen.

Volker

-- 
SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen
phone: +49-551-370000-0, fax: +49-551-370000-9
AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen
http://www.sernet.de, mailto:kontakt at sernet.de