#33011 [Opn->Bgs]: shmop: can still open segment for reading after shmop_delete
| From: | tony2001@php.net | Date: | Sat, 14 May 2005 17:34:18 +0000 |
| Subject: | #33011 [Opn->Bgs]: shmop: can still open segment for reading after shmop_delete | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-79010@lists.php.net to get a copy of this message | ||
ID: 33011
Updated by: tony2001@php.net
Reported By: joe at bs0 dot com
-Status: Open
+Status: Bogus
Bug Type: Semaphore related
Operating System: windows xp
PHP Version: 4.3.11, 5.0.4
New Comment:
"The segment will only actually be destroyed after the last process
detaches it (i.e., when the shm_nattch member of the associated
structure shmid_ds is zero)."
(c) man shmctl
Also read user notes here: http://php.net/shmop_delete
Previous Comments:
------------------------------------------------------------------------
[2005-05-12 04:33:53] joe at bs0 dot com
Description:
------------
Tested with iis/php5.0.4, iis/php4.3.11, apache2/php4.3.11 - same
problem. after a succesful call to shmop_delete, the shared memory can
still be opened, and the previous values read in. Delete call seems to
have no effect.
Each step is done in new request:
1)Create shared memory block, populate with string.
2)open block, read in string
3)open block, call shmop_delete (returns true)
4)open block, read in string <- should not be able to open block for
reading at this point.
looks to be the same as Bug #28965, this bug has status of No Feedback,
so opening a new one.
Reproduce code:
---------------
Code to reproduce:
http://bs0.com/shmop/shmop_test.php.txt
Expected result:
----------------
leave only one step uncommented at a time, at step 4, the open should
fail and no data should be read in.
Actual result:
--------------
After step 4, memory is still opened/data is read in.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=33011&edit=1