All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.com>
To: Steve French <smfrench@gmail.com>
Cc: CIFS <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:44:44 -0300	[thread overview]
Message-ID: <5d0f085859348bbd37fa2ec3b34426eb@manguebit.com> (raw)
In-Reply-To: <CAH2r5mu74CbSKRVi0P7LD57j3t=KxqLX_M6V+qvi-aRE2t9YTw@mail.gmail.com>

Steve French <smfrench@gmail.com> writes:

> What causes it to lose handle lease but still have read and write?

We don't know what caused it from the network traces we have.  I was
able to reproduce the downgrade from RWH to RW against Windows Server
2022 by mounting a share twice with 'nosharesock' and then having one
client writing to a file and the other client remaning the file's parent
directory.

For more information, see MS-SMB2 3.3.1.4.

  parent reply	other threads:[~2025-04-30 19:44 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
     [not found]     ` <CAH2r5mu74CbSKRVi0P7LD57j3t=KxqLX_M6V+qvi-aRE2t9YTw@mail.gmail.com>
2025-04-30 19:44       ` Paulo Alcantara [this message]
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=5d0f085859348bbd37fa2ec3b34426eb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.