cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [PATCH 06/10] locks: plumb an "aux" pointer into the setlease routines
Date: Sun, 24 Aug 2014 08:54:54 -0700	[thread overview]
Message-ID: <20140824155454.GE15908@infradead.org> (raw)
In-Reply-To: <20140824060801.5402880c@synchrony.poochiereds.net>

On Sun, Aug 24, 2014 at 06:08:01AM -0400, Jeff Layton wrote:
> > Can you just return -EEXIST if reusing an existing one and make it a
> > normal private pointer a we use elsewhere?
> > 
> 
> That sounds a little confusing...
> 
> We have two pointers we pass down to generic_setlease: the file_lock
> itself and with this patch, the "aux" pointer. We can end up using
> either, neither or both during a call to generic_setlease.
> 
> A simple error code can't properly indicate which of the two pointers
> got used. It might be clearer to turn the file_lock into a normal
> pointer and return -EEXIST if we reused it, but leave aux as a double
> pointer.

There is no way we could use a new file_lock but an existing
fasync_struct, as there won't be one on the newly allocated file_lock
structure, but otherwise you're right.

Just rename it to priv then and make me a little less grumpy ;-)



  reply	other threads:[~2014-08-24 15:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-23 14:41 [Cluster-devel] [PATCH 00/10] locks/nfsd: internal lease API overhaul Jeff Layton
2014-08-23 14:41 ` [Cluster-devel] [PATCH 01/10] locks: close potential race in lease_get_mtime Jeff Layton
2014-08-24 15:48   ` Christoph Hellwig
2014-08-25 20:01   ` J. Bruce Fields
2014-08-23 14:41 ` [Cluster-devel] [PATCH 02/10] nfsd: fix potential lease memory leak in nfs4_setlease Jeff Layton
2014-08-24 15:48   ` Christoph Hellwig
2014-08-23 14:41 ` [Cluster-devel] [PATCH 03/10] locks: generic_delete_lease doesn't need a file_lock at all Jeff Layton
2014-08-24  1:27   ` Christoph Hellwig
2014-08-24 10:09     ` Jeff Layton
2014-08-23 14:41 ` [Cluster-devel] [PATCH 04/10] locks: clean up vfs_setlease kerneldoc comments Jeff Layton
2014-08-24 15:51   ` Christoph Hellwig
2014-08-25 20:11     ` J. Bruce Fields
2014-08-23 14:41 ` [Cluster-devel] [PATCH 05/10] nfsd: don't keep a pointer to the lease in nfs4_file Jeff Layton
2014-08-24 15:51   ` Christoph Hellwig
2014-08-23 14:41 ` [Cluster-devel] [PATCH 06/10] locks: plumb an "aux" pointer into the setlease routines Jeff Layton
2014-08-24  1:33   ` Christoph Hellwig
2014-08-24 10:08     ` Jeff Layton
2014-08-24 15:54       ` Christoph Hellwig [this message]
2014-08-25 20:28   ` J. Bruce Fields
2014-08-26 10:53     ` Jeff Layton
2014-08-23 14:41 ` [Cluster-devel] [PATCH 07/10] locks: define a lm_setup handler for leases Jeff Layton
2014-08-24 15:58   ` Christoph Hellwig
2014-08-25  1:19     ` Jeff Layton
2014-08-26 13:58       ` Christoph Hellwig
2014-08-23 14:41 ` [Cluster-devel] [PATCH 08/10] locks: move i_lock acquisition into generic_*_lease handlers Jeff Layton
2014-08-24 16:06   ` Christoph Hellwig
2014-08-24 16:11     ` Christoph Hellwig
2014-08-31 14:51       ` Jeff Layton
2014-08-25  1:36     ` Jeff Layton
2014-08-23 14:41 ` [Cluster-devel] [PATCH 09/10] locks: move freeing of leases outside of i_lock Jeff Layton
2014-08-24 16:08   ` Christoph Hellwig
2014-08-25  1:35     ` Jeff Layton
2014-08-23 14:41 ` [Cluster-devel] [PATCH 10/10] locks: update Documentation/filesystems with lease API changes Jeff Layton
2014-08-24 16:10 ` [Cluster-devel] [PATCH 00/10] locks/nfsd: internal lease API overhaul Christoph Hellwig
2014-08-25  1:43   ` Jeff Layton
2014-08-26 13:59     ` Christoph Hellwig

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=20140824155454.GE15908@infradead.org \
    --to=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).