Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Paulo Alcantara <pc@manguebit.com>
To: Ronnie Sahlberg <lsahlber@redhat.com>,
	linux-cifs <linux-cifs@vger.kernel.org>
Cc: Steve French <smfrench@gmail.com>
Subject: Re: [PATCH 2/2] cifs: return a single-use cfid if we did not get a lease
Date: Fri, 17 Feb 2023 10:38:10 -0300	[thread overview]
Message-ID: <1ba6aed922e5a6b09a665c8df07b55ce@manguebit.com> (raw)
In-Reply-To: <20230217033501.2591185-2-lsahlber@redhat.com>

Ronnie Sahlberg <lsahlber@redhat.com> writes:

> If we did not get a lease we can still return a single use cfid to the caller.
> The cfid will not have has_lease set and will thus not be shared with any
> other concurrent users and will be freed immediately when the caller
> drops the handle.
>
> This avoids extra roundtrips for servers that do not support directory leases
> where they would first fail to get a cfid with a lease and then fallback
> to try a normal SMB2_open()
>
> Signed-off-by: Ronnie Sahlberg <lsahlber@redhat.com>
> ---
>  fs/cifs/cached_dir.c | 16 +++++++++++++---
>  1 file changed, 13 insertions(+), 3 deletions(-)

Reviewed-by: Paulo Alcantara (SUSE) <pc@manguebit.com>

  parent reply	other threads:[~2023-02-17 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  3:35 [PATCH 1/2] cifs: Check the lease context if we actually got a lease Ronnie Sahlberg
2023-02-17  3:35 ` [PATCH 2/2] cifs: return a single-use cfid if we did not get " Ronnie Sahlberg
2023-02-17  5:40   ` Steve French
2023-02-17  5:47     ` ronnie sahlberg
2023-02-17 13:38   ` Paulo Alcantara [this message]
2023-02-17 13:37 ` [PATCH 1/2] cifs: Check the lease context if we actually got " 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=1ba6aed922e5a6b09a665c8df07b55ce@manguebit.com \
    --to=pc@manguebit.com \
    --cc=linux-cifs@vger.kernel.org \
    --cc=lsahlber@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