From: Matthew Wilcox <matthew@wil.cx>
To: "William A.(Andy) Adamson" <andros@citi.umich.edu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Michael Kerrisk <mtk-lkml@gmx.net>,
heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org,
matthew@wil.cx, schwidefsky@de.ibm.com, michael.kerrisk@gmx.net
Subject: Re: fcntl: F_SETLEASE/F_RDLCK question
Date: Tue, 3 May 2005 14:59:46 +0100 [thread overview]
Message-ID: <20050503135946.GC19678@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20050503135542.BFBC61BB0E@citi.umich.edu>
On Tue, May 03, 2005 at 09:55:42AM -0400, William A.(Andy) Adamson wrote:
> i believe the current implementation is correct. opening a file for write
> means that you can not have a read lease, caller included.
Why not? Certainly, others will not be able to take out a read lease,
so there's very little point to only having a read lease, but I don't
see why we should deny it.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
next prev parent reply other threads:[~2005-05-03 13:59 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 [this message]
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
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=20050503135946.GC19678@parcelfarce.linux.theplanet.co.uk \
--to=matthew@wil.cx \
--cc=andros@citi.umich.edu \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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.