[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to write a proper fork hook code?

From: Svante Signell
Subject: Re: How to write a proper fork hook code?
Date: Mon, 02 Mar 2015 11:03:22 +0100

On Mon, 2015-03-02 at 10:57 +0100, Svante Signell wrote:
> On Mon, 2015-03-02 at 10:38 +0100, Samuel Thibault wrote:

> > > > But again, I'm still unsure why you believe that locks are being
> > > > inherited through fork(): before introducing a fork hook to forcibly
> > > > unlock something, one needs to be absolutely sure that it's actually
> > > > locked.  Actually it'd even look like a design flaw if two process could
> > > > actually hold a lock on the same piece of a file...

Well, the file record locking patches were mainly written by Neal. So if
you are so very expert on everything, maybe you could help me find where
the design flaw is. I have not managed to find it so far. The patches
have been submitted twice, latest (git mail) version starts with:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]