Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Pavel's Lock cleanup
Date: Fri, 14 Oct 2011 17:12:14 -0400	[thread overview]
Message-ID: <20111014211214.GA15319@fieldses.org> (raw)
In-Reply-To: <CAH2r5mtNGd-+YUXJwU2USPN_7XnQYdSaYh_HJrzyaM3g6o9szw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On Thu, Oct 13, 2011 at 05:23:52PM -0500, Steve French wrote:
> I like Pavel's lock cleanup (1st patch of series) so far, am
> continuing to review it, but I also noticed a few things that we need
> to do in the future. This line of code:
> 
> 	if (flock->fl_flags & FL_LEASE)
> 		cFYI(1, "Lease on file - not implemented yet");
> 
> reminded me that we should check if we need to implement this (in cifs
> we can return yes if we have a lease already (oplock), but in smb2.1
> and later we can request a lease or an upgrade to an existing one, on
> the fly).

And you'll also need to make sure you call break_lease() when you find
out it's broken.

A description of the smb (1/2/2.1) oplock and lease semantics would be
useful--I'm curious whether they're really a good fit for the linux
vfs's lease semantics.

--b.

  parent reply	other threads:[~2011-10-14 21:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13 22:23 Pavel's Lock cleanup Steve French
     [not found] ` <CAH2r5mtNGd-+YUXJwU2USPN_7XnQYdSaYh_HJrzyaM3g6o9szw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-14 21:12   ` J. Bruce Fields [this message]
     [not found]     ` <20111014211214.GA15319-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-10-14 22:38       ` Steve French
     [not found]         ` <CAH2r5msGZjEZP=BVWQedO80+W2yPJPvtd0+i5dAS9X0nq6=9kw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-14 23:29           ` J. Bruce Fields
     [not found]             ` <20111014232939.GA15881-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2011-10-15  0:02               ` Steve French
     [not found]                 ` <CAH2r5mvd+N_F897=jAjc7x=186YAHwe=jwQDD=JnOu8YFmu3qw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-15  0:04                   ` Steve French
     [not found]                     ` <CAH2r5mubN4RGznpLQbgLGSytaK-xM2Mz0dBNm-koKgBuUExPcQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-10-15 15:27                       ` Pavel Shilovsky
2011-10-15 14:50                   ` J. Bruce Fields

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=20111014211214.GA15319@fieldses.org \
    --to=bfields-uc3wqj2krung9huczpvpmw@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    /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