From: Mikhail Kruk <meshko@cs.brandeis.edu>
To: Jamie Lokier <jamie@shareable.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: fcntl file locking and pthreads
Date: Sun, 4 May 2003 09:25:14 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.33.0305040922020.32427-100000@iole.cs.brandeis.edu> (raw)
In-Reply-To: <20030504125845.GA32087@mail.jlokier.co.uk>
> Mikhail Kruk wrote:
> > on 2.4 kernels fcntl-based file locking does not work with
> > clone-based threads as expected (by me): two threads of the same process
> > can acquire exclusive lock on a file at the same time.
> > flock()-based locks work as expected, i.e. only one thread can have an
> > exclusive lock at a time.
>
> Is this true even when _not_ setting CLONE_FILES?
CLONE_FILES is an argument to clone(), I'm using pthreads and I don't
know if LinuxThreads implementation of pthreads gives me control of
how clone is called. Anyway, if I understand what CLONE_FILES does,
it should be given to clone, because threads do have to be able to share file
descriptors, probably. But not the locks!
next prev parent reply other threads:[~2003-05-04 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-04 6:13 fcntl file locking and pthreads Mikhail Kruk
2003-05-04 12:58 ` Jamie Lokier
2003-05-04 13:25 ` Mikhail Kruk [this message]
2003-05-04 15:24 ` Miquel van Smoorenburg
2003-05-04 18:40 ` David Schwartz
2003-05-04 19:29 ` Mikhail Kruk
2003-05-04 20:55 ` David Schwartz
2003-05-04 21:50 ` Mikhail Kruk
2003-05-04 21:29 ` Mark Mielke
2003-05-04 21:56 Ville Voutilainen
2003-05-04 22:04 ` Mikhail Kruk
2003-05-04 22:29 Ville Voutilainen
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=Pine.LNX.4.33.0305040922020.32427-100000@iole.cs.brandeis.edu \
--to=meshko@cs.brandeis.edu \
--cc=jamie@shareable.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).