Re: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory

From: Date: Sat, 01 Feb 2014 08:52:04 +0000
Subject: Re: Re: [VOTE] Introduce session.lock, session.lazy_write and session.lazy_destory
References: 1 2 3  Groups: php.internals 
Request: Send a blank email to [email protected] to get a copy of this message
Hello Yasuo,

On Saturday 01 February 2014 10:13:42 Yasuo Ohgaki wrote:
> Hi Patrick,
> 
> On Thu, Jan 30, 2014 at 3:37 PM, Patrick Schaaf <[email protected]> wrote:
> > Unrelated to the previous discussion, and applicable to the base PHP code
> > in mod_files.c too, another observation:
> > 
> > Some syscalls can fail with EINTR, when a signal hits while within the
> > kernel. This is especially true for flock(LOCK_EX) because in the already-
> > locked case the second call will go to sleep for a while waiting for the
> > lock to clear. But it is also possible, I think, for the pread/read/write
> > calls. The usual handling for the case (-1 return && errno == EINTR) is to
> > just repeat the call in a while loop. I think that at least doing so for
> > the LOCK_EX calls, would be prudent.
> 
> Could you send bug report for this and assign me?

Created https://bugs.php.net/bug.php?id=66623

Don't know how to assign that to you.

Thanks for taking care.

Patrick



Thread (42 messages)

« previous php.internals (#71914) next »