linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
To: Jeff Layton <jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
Cc: linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Christoph Hellwig <hch-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>,
	"J. Bruce Fields"
	<bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 13/17] locks: remove i_have_this_lease check from __break_lease
Date: Thu, 4 Sep 2014 10:51:32 -0700	[thread overview]
Message-ID: <20140904175132.GG16935@infradead.org> (raw)
In-Reply-To: <1409834323-7171-14-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>

On Thu, Sep 04, 2014 at 08:38:39AM -0400, Jeff Layton wrote:
> I think that the intent of this code was to ensure that a process won't
> deadlock if it has one fd open with a lease on it and then breaks that
> lease by opening another fd. In that case it'll treat the __break_lease
> call as if it were non-blocking.
> 
> This seems wrong -- the process could (for instance) be multithreaded
> and managing different fds via different threads. I also don't see any
> mention of this limitation in the (somewhat sketchy) documentation.
> 
> Remove the check and the non-blocking behavior when i_have_this_lease
> is true.

This looks reasonable to me, but I'm always very worried about changing
userspace exposed behavior..

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-09-04 17:51 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-04 12:38 [PATCH v2 00/17] locks: internal lease API overhaul Jeff Layton
2014-09-04 12:38 ` [PATCH v2 01/17] locks: consolidate "nolease" routines Jeff Layton
2014-09-04 12:41   ` Trond Myklebust
     [not found]     ` <CAHQdGtTqG8aW-cte2PW6pVw+OeCXATgr1BZwdhponuWMjzNg8g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-09-04 12:49       ` Jeff Layton
2014-09-04 18:25         ` Trond Myklebust
2014-09-04 20:12           ` Christoph Hellwig
     [not found]             ` <20140904201200.GA26054-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-09-05 11:48               ` Jeff Layton
     [not found]   ` <1409834323-7171-2-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 17:46     ` Christoph Hellwig
2014-09-04 12:38 ` [PATCH v2 02/17] security: make security_file_set_fowner, f_setown and __f_setown void return Jeff Layton
2014-09-04 17:47   ` Christoph Hellwig
2014-10-07 17:11   ` Dmitry Kasatkin
2014-10-07 17:17     ` Christoph Hellwig
     [not found]       ` <20141007171703.GA30274-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-10-07 17:34         ` Dmitry Kasatkin
2014-10-07 18:02           ` Jeff Layton
2014-09-04 12:38 ` [PATCH v2 03/17] locks: close potential race in lease_get_mtime Jeff Layton
2014-09-04 12:38 ` [PATCH v2 04/17] nfsd: fix potential lease memory leak in nfs4_setlease Jeff Layton
2014-09-04 12:38 ` [PATCH v2 05/17] locks: generic_delete_lease doesn't need a file_lock at all Jeff Layton
     [not found]   ` <1409834323-7171-6-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 20:14     ` Christoph Hellwig
     [not found]       ` <20140904201424.GB26054-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-09-05  0:29         ` Jeff Layton
2015-01-12 23:03     ` NeilBrown
2015-01-12 23:25       ` Jeff Layton
     [not found]         ` <20150112182500.33bebf6c-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2015-01-13  2:14           ` NeilBrown
2014-09-04 12:38 ` [PATCH v2 06/17] locks: clean up vfs_setlease kerneldoc comments Jeff Layton
2014-09-04 12:38 ` [PATCH v2 07/17] nfsd: don't keep a pointer to the lease in nfs4_file Jeff Layton
     [not found]   ` <1409834323-7171-8-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-05 21:40     ` J. Bruce Fields
     [not found]       ` <20140905214058.GA5443-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2014-09-06 12:33         ` Jeff Layton
2014-09-04 12:38 ` [PATCH v2 08/17] locks: plumb a "priv" pointer into the setlease routines Jeff Layton
2014-09-04 17:48   ` Christoph Hellwig
2014-09-04 12:38 ` [PATCH v2 10/17] locks: move i_lock acquisition into generic_*_lease handlers Jeff Layton
2014-09-04 12:38 ` [PATCH v2 11/17] locks: move freeing of leases outside of i_lock Jeff Layton
     [not found]   ` <1409834323-7171-12-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 17:50     ` Christoph Hellwig
2014-09-05 14:03       ` Jeff Layton
2014-09-04 12:38 ` [PATCH v2 12/17] locks: update Documentation/filesystems with new setlease semantics Jeff Layton
     [not found]   ` <1409834323-7171-13-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 17:50     ` Christoph Hellwig
     [not found]       ` <20140904175043.GF16935-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-09-05 14:02         ` Jeff Layton
2014-09-04 12:38 ` [PATCH v2 14/17] locks: __break_lease cleanup in preparation of allowing direct removal of leases Jeff Layton
     [not found]   ` <1409834323-7171-15-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 18:07     ` Christoph Hellwig
     [not found]       ` <20140904180725.GA11232-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-09-05 13:35         ` Jeff Layton
     [not found] ` <1409834323-7171-1-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 12:38   ` [PATCH v2 09/17] locks: define a lm_setup handler for leases Jeff Layton
     [not found]     ` <1409834323-7171-10-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 17:49       ` Christoph Hellwig
2014-09-04 12:38   ` [PATCH v2 13/17] locks: remove i_have_this_lease check from __break_lease Jeff Layton
     [not found]     ` <1409834323-7171-14-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 17:51       ` Christoph Hellwig [this message]
     [not found]         ` <20140904175132.GG16935-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-09-04 18:03           ` Jeff Layton
2014-09-04 12:38   ` [PATCH v2 15/17] locks: give lm_break a return value Jeff Layton
     [not found]     ` <1409834323-7171-16-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 18:08       ` Christoph Hellwig
2014-09-04 12:38   ` [PATCH v2 16/17] locks: set fl_owner for leases to filp instead of current->files Jeff Layton
2014-09-04 12:38 ` [PATCH v2 17/17] locks: clean up comments over fl_owner_t definition Jeff Layton
     [not found]   ` <1409834323-7171-18-git-send-email-jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
2014-09-04 17:53     ` Christoph Hellwig
     [not found]       ` <20140904175334.GH16935-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org>
2014-09-05 13:36         ` Jeff Layton

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=20140904175132.GG16935@infradead.org \
    --to=hch-wegcikhe2lqwvfeawa7xhq@public.gmane.org \
    --cc=bfields-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org \
    --cc=jlayton-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).