FW: Sporadic permission denied error in Samba 4.3 and 4.4, 4.2 OK

[Youzhong Yang]

>What message is being lost ? There are 4 messages:
>
>1) smbd -> smbd (request lease break - inter process messaging) 
>2). smbd -> client (request lease break - on the wire) 
>3). client -> smbd (lease break ack - on the wire).
>4). smbd -> smbd (broke lease - retry open - inter process messaging).

The first one.

>Under what circumstances does this occur ?

I don't know. I still don't have luck in reproducing the issue outside of our environment. It happens sporadically, but never in 4.2.x, no matter how many times I tried.

Thanks a lot,

--Youzhong

-----Original Message-----
From: Jeremy Allison [mailto:jra at samba.org] 
Sent: Monday, November 14, 2016 3:01 PM
To: Youzhong Yang <Youzhong.Yang at mathworks.com>
Cc: samba-technical at lists.samba.org
Subject: Re: FW: Sporadic permission denied error in Samba 4.3 and 4.4, 4.2 OK

On Mon, Nov 14, 2016 at 07:45:14PM +0000, Youzhong Yang wrote:
> Thanks Jeremy.
> 
> Base on your comment, I enabled debug output in the following places:
> 
> source3/smbd/open.c: send_break_message()
>        DEBUG(0, ("Sending break request to PID %s for %s break_to %u\n",
>                   server_id_str_buf(exclusive->pid, &tmp), 
> file_id_string_tos(&exclusive->id), break_to));
> 
> source3/lib/messages.c: messaging_recv_cb()
>         DEBUG(0, ("%s: Received message 0x%x len %u (num_fds:%u) from %s\n",
>                    __func__, (unsigned)rec.msg_type,
>                    (unsigned)rec.buf.length,
>                    (unsigned)num_fds,
>                    server_id_str_buf(rec.src, &idbuf)));
> 
> source3/smbd/oplock.c: process_oplock_break_message()
>        DEBUG(0, ("Got oplock break to %u message from pid %s: %s/%llu\n",
>                   (unsigned)break_to, server_id_str_buf(src, &tmp),
>                   file_id_string_tos(&msg.id),
>                   (unsigned long long)msg.share_file_id));
> 
> The issue is not that the Windows client didn't respond to lease break request - sometimes the break message was lost, never received by the corresponding smbd process.
> 
> Since we don't have this issue in Samba 4.2.x, I think most likely something in the messaging system caused the problem. I am still struggling to find out.