public inbox for linux-cifs@vger.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.com>
To: Steve French <smfrench@gmail.com>
Cc: linux-cifs@vger.kernel.org, David Howells <dhowells@redhat.com>,
	Pierguido Lambri <plambri@redhat.com>,
	Bharath S M <bharathsm@microsoft.com>
Subject: Re: [PATCH] smb: client: fix delay on concurrent opens
Date: Wed, 30 Apr 2025 16:14:42 -0300	[thread overview]
Message-ID: <2f76f9b0b3e5ca99fce360d19b0d6218@manguebit.com> (raw)
In-Reply-To: <CAH2r5muGNUp9UqQZ_mPVoLiw9+xocV8OZ8hubGyQG=oTd=-BXQ@mail.gmail.com>

Steve French <smfrench@gmail.com> writes:

> Did you mean
>
> downgraded "RWH to RW"  or downgraded from "RWH to RH"

Downgraded from RWH to RW.

> But it is puzzling why file would still be open if not in openfile list

The server is breaking the H lease.  cifs_close_deferred_file() will put
all cifsFileInfo references from deferred closes in the inode, meaning
that _cifsFileInfo_put() call in cifs_oplock_break() will effectively
put the last reference and then closing the open handle.

The check for a non-empty list after that makes no sense as we already
closed all open handles.  As I understand it, the implicit ACK would
work if we have no open handles at the time we receive the lease break,
but that couldn't work as we always get an active reference of the open
handle before processing the lease break.

What am I missing?

  reply	other threads:[~2025-04-30 19:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28 14:05 [PATCH] smb: client: fix delay on concurrent opens Paulo Alcantara
2025-04-28 14:40 ` Steve French
2025-04-28 14:44   ` Paulo Alcantara
2025-04-30 14:15 ` Steve French
2025-04-30 19:14   ` Paulo Alcantara [this message]
     [not found]     ` <CAH2r5mu74CbSKRVi0P7LD57j3t=KxqLX_M6V+qvi-aRE2t9YTw@mail.gmail.com>
2025-04-30 19:44       ` Paulo Alcantara
2025-05-05 10:41     ` Bharath SM
2025-05-05 13:12       ` Paulo Alcantara
2025-05-05 14:16         ` Bharath SM
2025-05-05 15:05           ` Paulo Alcantara
2025-05-09 11:22             ` Shyam Prasad N
2025-05-12 13:31               ` Paulo Alcantara
2025-05-12 22:47                 ` Steve French
2025-05-12 22:57                   ` Paulo Alcantara

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2f76f9b0b3e5ca99fce360d19b0d6218@manguebit.com \
    --to=pc@manguebit.com \
    --cc=bharathsm@microsoft.com \
    --cc=dhowells@redhat.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=plambri@redhat.com \
    --cc=smfrench@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox