This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: STC for libapr1 failure

On Feb 15 11:39, David Rothenberger wrote:
> On 2/15/2012 7:38 AM, Corinna Vinschen wrote:
> > Did I mention that I hate synchronization problems?  Anyway, I think I
> > found the problem.  I applied a patch which fixes the problem for me
> > and, surprise!, the flock test still runs fine, too.  I've just uploaded
> > a new snapshot.  Please give it a try.
> All the procmutex tests pass now! Awesome!
> But... now one of the flock tests is failing. It takes a while to
> extract a STC from the APR test suite because everything is written in
> APR-ese and I have to convert every APR call into the base C library
> calls. I'll work on that over the next day or three.
> The gist of the test that's failing is this:
>  * Create a file.
>  * Get an exclusive flock on it.
>  * Spawn a child process that attempts to get an exclusive, non-blocking
>    lock on the file.
> The test is expecting that the child will not be able to get the lock,
> but the child is able to.

Did I really mention that I hate synchronization problems?

Does it fork/exec or does it only exec?  If the latter, and if the child
uses the file descriptor inherited from the parent, then it's ok that
it gets the lock, afaics.  From the Linux man page:

   Locks  created by flock() are associated with an open file table entry.
   This means that duplicate file descriptors (created  by,  for  example,
   fork(2)  or  dup(2)) refer to the same lock, and this lock may be modiâ
   fied or released using any of these descriptors.  Furthermore, the lock
   is  released  either  by  an explicit LOCK_UN operation on any of these
   duplicate descriptors, or when all such descriptors have been closed.
   Locks created by flock() are preserved across an execve(2)

But maybe I misunderstood something when implementig this?  I guess I really
need the testcase.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]