Hi Heiko, On Mon, 2 May 2005 11:15:24 +0200 Heiko Carstens <[email protected]> wrote: > > the semantics of fnctl used together with F_SETLEASE and > argument F_RDLCK have been changed with bk changeset > 1.1938.185.141 (sometime between 2.6.9 and 2.6.10). > Since then it's only possible to get a read lease when the > file in question does not have _any_ writers. > This is at least inconsistent with the man page of fcntl > and looks pretty much like this is a bug in the kernel. > > Any comments? The previous behaviour was a bug that occurred because at the time the original lease code was written, it was not possible to tell if there were writers when the read lease was being taken. Further improvements in the kernel have since made this possible. The intention of a read lease is to let the holder know is anyone tries to modify the file. The current behaviour does not conflict with the man pages on Debian (although the previous behaviour did not either :-)) -- Cheers, Stephen Rothwell [email protected] http://www.canb.auug.org.au/~sfr/
Attachment:
pgpAx05Q05ZBP.pgp
Description: PGP signature
- Follow-Ups:
- Re: fcntl: F_SETLEASE/F_RDLCK question
- From: "Michael Kerrisk" <[email protected]>
- Re: fcntl: F_SETLEASE/F_RDLCK question
- From: Heiko Carstens <[email protected]>
- Re: fcntl: F_SETLEASE/F_RDLCK question
- References:
- fcntl: F_SETLEASE/F_RDLCK question
- From: Heiko Carstens <[email protected]>
- fcntl: F_SETLEASE/F_RDLCK question
- Prev by Date: Re: [2.6 patch] __deprecated_for_modules insert_resource
- Next by Date: kernel bug ?
- Previous by thread: fcntl: F_SETLEASE/F_RDLCK question
- Next by thread: Re: fcntl: F_SETLEASE/F_RDLCK question
- Index(es):