From: Mike Frysinger <vapier@gentoo.org>
To: libc-alpha@sourceware.org
Cc: Jeff Layton <jlayton@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH 0/2] glibc: header file and manual updates for file-private locks
Date: Sun, 16 Feb 2014 03:27:05 -0500 [thread overview]
Message-ID: <2582214.4RaFrulCEQ@vapier> (raw)
In-Reply-To: <1392145436-13983-1-git-send-email-jlayton@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On Tuesday, February 11, 2014 14:03:54 Jeff Layton wrote:
> I've been working on a set of patches to add a new type file record lock
> to the Linux kernel that have less troublesome semantics on close and
> that are usable by threaded applications.
>
> I have a blog post here with more details:
>
>
> http://jtlayton.wordpress.com/2014/01/07/file-private-posix-locks-aka-un-po
> six-locks/
>
> ...and the latest kernel patchset is here:
>
> https://lkml.org/lkml/2014/1/14/554
>
> This patchset represents a set of corresponding updates for glibc. It
> just adds the new cmd values to fcntl.h, and a manual update that
> discusses how to use the new locks.
>
> I'm currently shooting for a merge in v3.15 kernel so I'm posting this
> as an RFC for now.
disclaimer: haven't read the kernel patches. just the patch summary and your
blog post.
looks like the new API manipulates the existing POSIX lock only -- flock based
locks are still parallel. too crazy to have the new API grab both since
you're bringing proper semantics that cover both ?
a good summary of Linux locking from the perspective of userspace was posted
here sometime ago:
http://0pointer.de/blog/projects/locking.html
random notes/limitations/bugs are also in the various man pages like fcntl(2)
would be nice if we could cover as many known limitations as possible with the
new api so as to not need yet another in the future ;)
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-16 8:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 19:03 [RFC][PATCH 0/2] glibc: header file and manual updates for file-private locks Jeff Layton
2014-02-11 19:03 ` [RFC][PATCH 1/2] fcntl.h: add new definitions for file-private lock cmd values Jeff Layton
2014-02-11 21:49 ` Roland McGrath
2014-02-11 23:57 ` Jeff Layton
2014-02-12 7:50 ` Andreas Schwab
2014-02-12 23:19 ` Roland McGrath
2014-02-11 19:03 ` [RFC][PATCH 2/2] manual: update manual to document file-private locks Jeff Layton
2014-02-16 8:27 ` Mike Frysinger [this message]
2014-02-16 12:42 ` [RFC][PATCH 0/2] glibc: header file and manual updates for " 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=2582214.4RaFrulCEQ@vapier \
--to=vapier@gentoo.org \
--cc=jlayton@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-fsdevel@vger.kernel.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).