Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-11 Thread J. Bruce Fields
On Mon, Mar 11, 2013 at 11:18:15AM -0700, Andy Lutomirski wrote: > On Tue, Mar 5, 2013 at 11:07 AM, Simo wrote: > > On 03/05/2013 01:13 PM, J. Bruce Fields wrote: > >> > >> On Mon, Mar 04, 2013 at 05:49:46PM -0500, Simo wrote: > >>> > >>> On 03/04/2013 04:19 PM, J. Bruce Fields wrote: > > >>>

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-11 Thread Andy Lutomirski
On Tue, Mar 5, 2013 at 11:07 AM, Simo wrote: > On 03/05/2013 01:13 PM, J. Bruce Fields wrote: >> >> On Mon, Mar 04, 2013 at 05:49:46PM -0500, Simo wrote: >>> >>> On 03/04/2013 04:19 PM, J. Bruce Fields wrote: On Thu, Feb 28, 2013 at 01:53:25PM -0800, Andy Lutomirski wrote: > > [p

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-11 Thread Pavel Shilovsky
2013/3/5 Simo : > On 03/05/2013 01:13 PM, J. Bruce Fields wrote: >> >> On Mon, Mar 04, 2013 at 05:49:46PM -0500, Simo wrote: >>> >>> On 03/04/2013 04:19 PM, J. Bruce Fields wrote: I'm a little more worried: these are mandatory locks, and applications that use them are used to the locks be

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-05 Thread Simo
On 03/05/2013 01:13 PM, J. Bruce Fields wrote: On Mon, Mar 04, 2013 at 05:49:46PM -0500, Simo wrote: On 03/04/2013 04:19 PM, J. Bruce Fields wrote: On Thu, Feb 28, 2013 at 01:53:25PM -0800, Andy Lutomirski wrote: [possible resend -- sorry] On 02/28/2013 07:25 AM, Pavel Shilovsky wrote: This

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-05 Thread J. Bruce Fields
On Mon, Mar 04, 2013 at 05:49:46PM -0500, Simo wrote: > On 03/04/2013 04:19 PM, J. Bruce Fields wrote: > >On Thu, Feb 28, 2013 at 01:53:25PM -0800, Andy Lutomirski wrote: > >>[possible resend -- sorry] > >> > >>On 02/28/2013 07:25 AM, Pavel Shilovsky wrote: > >>>This patchset adds support of O_DENY

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-04 Thread Simo
On 03/04/2013 04:19 PM, J. Bruce Fields wrote: On Thu, Feb 28, 2013 at 01:53:25PM -0800, Andy Lutomirski wrote: [possible resend -- sorry] On 02/28/2013 07:25 AM, Pavel Shilovsky wrote: This patchset adds support of O_DENY* flags for Linux fs layer. These flags can be used by any application

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-04 Thread J. Bruce Fields
On Thu, Feb 28, 2013 at 01:53:25PM -0800, Andy Lutomirski wrote: > [possible resend -- sorry] > > On 02/28/2013 07:25 AM, Pavel Shilovsky 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 orga

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-03-01 Thread David Laight
On Thu, Feb 28, 2013 at 01:53:25PM -0800, Andy Lutomirski wrote: > > O_DENYMAND - to switch on/off three flags above. > > O_DENYMAND doesn't deny anything. Would a name like O_RESPECT_DENY be > better? Possibly rename to O_CHECK_DENY ? David -- David Laight: da...@l8s.co.uk -- To unsu

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-02-28 Thread Pavel Shilovsky
2013/3/1 Andy Lutomirski : > [possible resend -- sorry] > > On 02/28/2013 07:25 AM, Pavel Shilovsky 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 s

Re: [PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-02-28 Thread Andy Lutomirski
[possible resend -- sorry] On 02/28/2013 07:25 AM, Pavel Shilovsky 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 i

[PATCH v3 0/7] Add O_DENY* support for VFS and CIFS/NFS

2013-02-28 Thread Pavel Shilovsky
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