From: Andrea Arcangeli <andrea@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John Covici <covici@ccs.covici.com>, linux-kernel@vger.kernel.org
Subject: Re: is flock broken in 2.4 or 2.5 kernels or what does this mean?
Date: Wed, 24 Jul 2002 01:20:19 +0200 [thread overview]
Message-ID: <20020723232019.GV1117@dualathlon.random> (raw)
In-Reply-To: <1027441872.31787.139.camel@irongate.swansea.linux.org.uk>
On Tue, Jul 23, 2002 at 05:31:12PM +0100, Alan Cox wrote:
> On Tue, 2002-07-23 at 15:41, John Covici wrote:
> > In the latest release notes of sendmail I have read the following:
> >
> > NOTE: Linux appears to have broken flock() again. Unless
> > the bug is fixed before sendmail 8.13 is shipped,
> > 8.13 will change the default locking method to
> > fcntl() for Linux kernel 2.4 and later. You may
> > want to do this in 8.12 by compiling with
> > -DHASFLOCK=0. Be sure to update other sendmail
> > related programs to match locking techniques.
> >
> > Can anyone tell me what this is all about -- is there any basis in
> > reality for what they are saying?
>
> First I've heard of it, so it would be useful if someone has access to
> the sendmail problem report/test in question that shows it and I'll go
> find out.
fix is in -aa from Matthew Wilcox:
http://www.us.kernel.org/pub/linux/kernel/people/andrea/kernels/v2.4/2.4.19rc3aa1/00_drop-broken-flock-account-1
fcntl API never obeyed to the accounting anyways.
Andrea
next prev parent reply other threads:[~2002-07-23 23:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 14:41 is flock broken in 2.4 or 2.5 kernels or what does this mean? John Covici
2002-07-23 16:31 ` Alan Cox
2002-07-23 15:27 ` Richard A Nelson
2002-07-23 15:50 ` Jirka Kosina
2002-07-23 21:44 ` J.A. Magallon
2002-07-24 16:08 ` David Ford
2002-07-25 1:28 ` Alan Cox
2002-07-23 23:20 ` Andrea Arcangeli [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-23 23:28 dank
2002-07-23 23:31 ` dank
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=20020723232019.GV1117@dualathlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=covici@ccs.covici.com \
--cc=linux-kernel@vger.kernel.org \
/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.