On Thu, Feb 07, 2013 at 01:53:46PM +0400, Pavel Shilovsky wrote:
2013/2/5 J. Bruce Fields bfie...@fieldses.org:
On Tue, Feb 05, 2013 at 03:45:31PM +0400, Pavel Shilovsky wrote:
2013/1/31 J. Bruce Fields bfie...@fieldses.org:
On Thu, Jan 17, 2013 at 08:52:59PM +0400, Pavel Shilovsky wrote:
On Thu, Feb 07, 2013 at 06:32:38PM +0400, Pavel Shilovsky wrote:
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
On Thu, Feb 07, 2013 at 01:53:46PM +0400, Pavel Shilovsky wrote:
Nothing prevents it. If somebody grabbed a share mode lock on a file
before we call deny_lock_file, we simply
On Thu, Feb 07, 2013 at 08:00:13PM +0400, Pavel Shilovsky wrote:
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
On Thu, Feb 07, 2013 at 06:32:38PM +0400, Pavel Shilovsky wrote:
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
On Thu, Feb 07, 2013 at 01:53:46PM +0400, Pavel Shilovsky wrote:
On Thu, Feb 07, 2013 at 08:50:16PM +0400, Pavel Shilovsky wrote:
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
That would be a bug, I think. E.g. man 3posix open:
No files shall be created or modified if the function returns
-1.
Looking at the code... See the
2013/2/5 J. Bruce Fields bfie...@fieldses.org:
On Tue, Feb 05, 2013 at 03:45:31PM +0400, Pavel Shilovsky wrote:
2013/1/31 J. Bruce Fields bfie...@fieldses.org:
On Thu, Jan 17, 2013 at 08:52:59PM +0400, Pavel Shilovsky wrote:
If O_DENYMAND flag is specified, O_DENYREAD/WRITE/MAND flags are
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
On Thu, Feb 07, 2013 at 01:53:46PM +0400, Pavel Shilovsky wrote:
Nothing prevents it. If somebody grabbed a share mode lock on a file
before we call deny_lock_file, we simply close this file and return
-ETXTBSY.
But leave the newly-created file
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
On Thu, Feb 07, 2013 at 06:32:38PM +0400, Pavel Shilovsky wrote:
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
On Thu, Feb 07, 2013 at 01:53:46PM +0400, Pavel Shilovsky wrote:
Nothing prevents it. If somebody grabbed a share mode lock on a file
2013/2/7 J. Bruce Fields bfie...@fieldses.org:
That would be a bug, I think. E.g. man 3posix open:
No files shall be created or modified if the function returns
-1.
Looking at the code... See the references to FILE_CREATED in
atomic_open--looks like that's trying to
2013/1/31 J. Bruce Fields bfie...@fieldses.org:
On Thu, Jan 17, 2013 at 08:52:59PM +0400, Pavel Shilovsky wrote:
If O_DENYMAND flag is specified, O_DENYREAD/WRITE/MAND flags are
translated to flock's flags:
!O_DENYREAD - LOCK_READ
!O_DENYWRITE - LOCK_WRITE
O_DENYMAND - LOCK_MAND
and
On Tue, Feb 05, 2013 at 03:45:31PM +0400, Pavel Shilovsky wrote:
2013/1/31 J. Bruce Fields bfie...@fieldses.org:
On Thu, Jan 17, 2013 at 08:52:59PM +0400, Pavel Shilovsky wrote:
If O_DENYMAND flag is specified, O_DENYREAD/WRITE/MAND flags are
translated to flock's flags:
!O_DENYREAD -
On Thu, Jan 17, 2013 at 08:52:59PM +0400, Pavel Shilovsky wrote:
If O_DENYMAND flag is specified, O_DENYREAD/WRITE/MAND flags are
translated to flock's flags:
!O_DENYREAD - LOCK_READ
!O_DENYWRITE - LOCK_WRITE
O_DENYMAND - LOCK_MAND
and set through flock_lock_file on a file.
This
11 matches
Mail list logo