From: "J. Bruce Fields" <bfields@fieldses.org>
To: Michael Kerrisk <michael.kerrisk@gmx.net>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
mtk-lkml@gmx.net, heiko.carstens@de.ibm.com,
linux-kernel@vger.kernel.org, andros@citi.umich.edu,
matthew@wil.cx, schwidefsky@de.ibm.com
Subject: Re: fcntl: F_SETLEASE/F_RDLCK question
Date: Tue, 31 May 2005 11:23:28 -0400 [thread overview]
Message-ID: <20050531152328.GC22433@fieldses.org> (raw)
In-Reply-To: <32555.1117551230@www14.gmx.net>
On Tue, May 31, 2005 at 04:53:50PM +0200, Michael Kerrisk wrote:
> I applied this against 2.6.12-rc4, and it fixes the problem
> (and I've also teasted various other facets of file leases
> and this change causes no obvious breakage elsewhere).
>
> Are you going to push this fix into 2.6.12?
Are you sure this is actually a problem?
I still have the following questions I had before:
> I'm a little confused as to why anyone would have the expectation
> that read leases would not conflict with write opens by the same
> process, given that break_lease() has never functioned that way, so
> later write opens by the same process have always broken any read lease.
>
> Are there applications that actually depend on the old behaviour? Is
> there any documentation that blesses it? All I can find is the fcntl
> man page, and as far as I can tell an implementation that makes read
> leases conflict with all write opens (by the same process or not) is
> consistent with that man page.
--b.
next prev parent reply other threads:[~2005-05-31 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-02 9:15 fcntl: F_SETLEASE/F_RDLCK question Heiko Carstens
2005-05-02 11:04 ` Stephen Rothwell
2005-05-02 12:10 ` Heiko Carstens
2005-05-03 10:00 ` Michael Kerrisk
2005-05-03 13:14 ` Stephen Rothwell
2005-05-03 13:55 ` William A.(Andy) Adamson
2005-05-03 13:59 ` Matthew Wilcox
2005-05-03 14:15 ` William A.(Andy) Adamson
2005-05-03 14:50 ` Michael Kerrisk
2005-05-03 16:21 ` William A.(Andy) Adamson
2005-05-03 16:36 ` J. Bruce Fields
2005-05-31 14:53 ` Michael Kerrisk
2005-05-31 15:23 ` J. Bruce Fields [this message]
2005-05-31 15:41 ` Michael Kerrisk
2005-05-31 15:34 ` File leases and fork() Michael Kerrisk
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=20050531152328.GC22433@fieldses.org \
--to=bfields@fieldses.org \
--cc=andros@citi.umich.edu \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=michael.kerrisk@gmx.net \
--cc=mtk-lkml@gmx.net \
--cc=schwidefsky@de.ibm.com \
--cc=sfr@canb.auug.org.au \
/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.