Req #35894 [Com]: php-imap doesn't trap USR2 when mailbox is locked

From: Date: Thu, 18 Aug 2022 22:26:17 +0000
Subject: Req #35894 [Com]: php-imap doesn't trap USR2 when mailbox is locked
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-242249@lists.php.net to get a copy of this message 
Edit report at https://bugs.php.net/bug.php?id=35894&edit=1

 ID:                 35894
 Comment by:         sample at email dot tst
 Reported by:        jik at kamens dot brookline dot ma dot us
 Summary:            php-imap doesn't trap USR2 when mailbox is locked
 Status:             Analyzed
 Type:               Feature/Change Request
 Package:            IMAP related
 Operating System:   Linux
 PHP Version:        5.1.2
 Block user comment: N
 Private report:     N

 New Comment:

1


Previous Comments:
------------------------------------------------------------------------
[2022-08-18 22:26:11] sample at email dot tst

1

------------------------------------------------------------------------
[2010-01-10 22:36:08] rasmus@php.net

The problem with PHP setting a handler for SIGUSR2 is that when we are 
running as a SAPI module inside some other process like Apache or 
anything using LinuxThreads, grabbing SIGUSR2 may cause problems.  
Newer Linux kernels provide reserved internals signals for LinuxThreads 
to use, and Apache should only be using SIGUSR1, but how confident are 
you that PHP grabbing this signal isn't going to break it in some 
environments?  It may fix the problem in yours, but if it breaks it in 
many others that is something we need to deal with.

------------------------------------------------------------------------
[2010-01-10 21:45:30] tdfischer at fedoraproject dot org

This bug is still around and can wreak havok for a drupal site that lets 
users submit content via machine-local mail. Could someone *please* 
commit it already?

------------------------------------------------------------------------
[2006-01-05 15:56:17] jik at kamens dot brookline dot ma dot us

You *don't* want to allow the simultaneous opening of a mailbox by two processes.  The whole
point of locking is to *prevent* the simultaneous opening of a mailbox by two processes.  What the
locking is *supposed* to do is to make one process *wait* for the other one, but what it does
instead, if you don't catch the USR2 signal, is for the process that got the lock first to
*die* after *being killed* by the other one.  This is not correct behavior.

Incidentally, I just tested with a newly compiled c-client 2004g and confirmed that the problem
persists there without my patch.

------------------------------------------------------------------------
[2006-01-05 10:07:30] sniper@php.net

Why would you want to allow opening same mailbox by two simultaneous processes?

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=35894


--
Edit this bug report at https://bugs.php.net/bug.php?id=35894&edit=1

Thread (45 messages)

« previous php.bugs (#242249) next »