All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
To: Pavel Shilovsky <piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	wine-devel-5vRYHf7vrtgdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH v2 0/8] Add O_DENY* support for VFS and CIFS/NFS
Date: Fri, 18 Jan 2013 09:55:38 +1100	[thread overview]
Message-ID: <20130118095538.fdd0b3be90739b9fd9179b5d@canb.auug.org.au> (raw)
In-Reply-To: <1358441537-8672-1-git-send-email-piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

Hi Pavel,

On Thu, 17 Jan 2013 20:52:09 +0400 Pavel Shilovsky <piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org> wrote:
>
> This patchset adds support of O_DENY* flags for Linux fs layer. These flags can be used by any application that needs share reservations to organize a file access. VFS already has some sort of this capability - now it's done through flock/LOCK_MAND mechanis, but that approach is non-atomic. This patchset build new capabilities on top of the existing one but doesn't bring any changes into the flock call semantic.

This has probably been discussed, but is Linux's leases implementation
not sufficient?  Just wondering.

-- 
Cheers,
Stephen Rothwell                    sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pavel Shilovsky <piastry@etersoft.ru>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-cifs@vger.kernel.org, linux-nfs@vger.kernel.org,
	wine-devel@winehq.org
Subject: Re: [PATCH v2 0/8] Add O_DENY* support for VFS and CIFS/NFS
Date: Fri, 18 Jan 2013 09:55:38 +1100	[thread overview]
Message-ID: <20130118095538.fdd0b3be90739b9fd9179b5d@canb.auug.org.au> (raw)
In-Reply-To: <1358441537-8672-1-git-send-email-piastry@etersoft.ru>

[-- Attachment #1: Type: text/plain, Size: 698 bytes --]

Hi Pavel,

On Thu, 17 Jan 2013 20:52:09 +0400 Pavel Shilovsky <piastry@etersoft.ru> wrote:
>
> This patchset adds support of O_DENY* flags for Linux fs layer. These flags can be used by any application that needs share reservations to organize a file access. VFS already has some sort of this capability - now it's done through flock/LOCK_MAND mechanis, but that approach is non-atomic. This patchset build new capabilities on top of the existing one but doesn't bring any changes into the flock call semantic.

This has probably been discussed, but is Linux's leases implementation
not sufficient?  Just wondering.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2013-01-17 22:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 16:52 [PATCH v2 0/8] Add O_DENY* support for VFS and CIFS/NFS Pavel Shilovsky
2013-01-17 16:52 ` Pavel Shilovsky
     [not found] ` <1358441537-8672-1-git-send-email-piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org>
2013-01-17 22:55   ` Stephen Rothwell [this message]
2013-01-17 22:55     ` Stephen Rothwell
2013-01-18  6:29     ` Pavel Shilovsky
2013-01-30 22:11   ` J. Bruce Fields
2013-01-30 22:11     ` J. Bruce Fields
     [not found]     ` <20130130221118.GB15584-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-02-05 11:33       ` Pavel Shilovsky
2013-02-05 11:33         ` Pavel Shilovsky
     [not found]         ` <CAKywueQcia1jJfdVJFzfHdc5zQ_86r3T4bmee9cpP18qqbcLFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-02-05 14:38           ` J. Bruce Fields
2013-02-05 14:38             ` J. Bruce Fields
     [not found]             ` <20130205143813.GB9886-uC3wQj2KruNg9hUCZPvPmw@public.gmane.org>
2013-02-07  9:40               ` Pavel Shilovsky
2013-02-07  9:40                 ` Pavel Shilovsky

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=20130118095538.fdd0b3be90739b9fd9179b5d@canb.auug.org.au \
    --to=sfr-3fnu+uhb4dndw9hx6icosa@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-fsdevel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-nfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=piastry-7qunaywFIewox3rIn2DAYQ@public.gmane.org \
    --cc=wine-devel-5vRYHf7vrtgdnm+yROfE0A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.