From: Andy Lutomirski <luto@amacapital.net>
To: Jeff Layton <jlayton@redhat.com>
Cc: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Bruce Fields <bfields@fieldses.org>,
trond.myklebust@primarydata.com
Subject: Re: [PATCH 2/2] locks: make locks_mandatory_area check for file-private locks
Date: Mon, 10 Mar 2014 10:07:10 -0700 [thread overview]
Message-ID: <CALCETrVoYo39a-tPoMXUw-oqkVeuBE6vmrWWn8tN0MuhusJfhg@mail.gmail.com> (raw)
In-Reply-To: <1394458607-23579-3-git-send-email-jlayton@redhat.com>
On Mon, Mar 10, 2014 at 6:36 AM, Jeff Layton <jlayton@redhat.com> wrote:
> Allow locks_mandatory_area() to handle file-private locks correctly.
> If there is a file-private lock set on an open file and we're doing I/O
> via the same, then that should not cause anything to block.
>
> Handle this by first doing a non-blocking FL_ACCESS check for a
> file-private lock, and then fall back to checking for a classic POSIX
> lock (and possibly blocking).
This is ugly, but it doesn't seem much worse than the existing code. :)
--Andy
next prev parent reply other threads:[~2014-03-10 17:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 13:36 [PATCH 0/2] locks: allow mandatory locking to work with file-private locks Jeff Layton
2014-03-10 13:36 ` [PATCH 1/2] locks: fix locks_mandatory_locked to respect " Jeff Layton
2014-03-10 19:04 ` J. Bruce Fields
2014-03-10 13:36 ` [PATCH 2/2] locks: make locks_mandatory_area check for " Jeff Layton
2014-03-10 17:07 ` Andy Lutomirski [this message]
2014-03-10 17:31 ` Jeffrey Layton
2014-03-10 17:37 ` Andy Lutomirski
2014-03-10 17:47 ` Jeffrey Layton
2014-03-10 19:21 ` [PATCH 0/2] locks: allow mandatory locking to work with " J. Bruce Fields
2014-03-10 19:31 ` Jeffrey Layton
2014-03-10 19:37 ` 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=CALCETrVoYo39a-tPoMXUw-oqkVeuBE6vmrWWn8tN0MuhusJfhg@mail.gmail.com \
--to=luto@amacapital.net \
--cc=bfields@fieldses.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=trond.myklebust@primarydata.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;
as well as URLs for NNTP newsgroup(s).