#33011 [Asn-Opn]: [PATCH] shmop: can still open segment for reading after shmop_delete

[jani]

 ID:   33011
 Updated by:   [EMAIL PROTECTED]
 Reported By:  joe at bs0 dot com
-Status:   Assigned
+Status:   Open
 Bug Type: Semaphore related
 Operating System: win32 only
-PHP Version:  5.0.4
+PHP Version:  5.2.6
 Assigned To:  iliaa


Previous Comments:


[2008-06-07 02:58:13] pmvcallan at gmail dot com

Same problem running apache 2, php 5.2.6 on windows.

Attempted closing then deleting and deleting then closing the block,
returns true in both cases.
Still leaves the block and contents intact regardless.



[2007-07-18 04:01:18] [EMAIL PROTECTED]

Just noting two things: one, the patch is no longer online and two,
Ilia doesn't really 'do' Windows any more.

I looked at it but don't have time to play right now, not least because
I don't have a current copy of PHP on board. I _think_ it probably just
needs a flag setting in shmctl() (in tsrm_win32.c) when it's called from
shmop_delete() - not sure. Something like:

shm-descriptor-shm_perm.mode = IPC_EXCL;

- but again not sure, there's a copy flying around there somewhere. I'd
need to test.



[2007-07-13 20:55:38] jmccaskey at gmail dot com

I'm experiencing this same issue on PHP 5.2.2 under Apache 2 on
windows.   How is it that this issue was opened years ago and is not
fixed?



[2006-04-15 16:43:52] piotrprz at gmail dot com

PHP 5.1.2 still has this bug: apache2/php5.1.2 on windows xp



[2005-11-07 00:03:11] [EMAIL PROTECTED]

Ilia, have you checked the patch in this report yet?




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
http://bugs.php.net/33011

-- 
Edit this bug report at http://bugs.php.net/?id=33011edit=1

#33011 [Asn-Opn]: [PATCH] shmop: can still open segment for reading after shmop_delete

[sniper]

 ID:   33011
 Updated by:   [EMAIL PROTECTED]
 Reported By:  joe at bs0 dot com
-Status:   Assigned
+Status:   Open
 Bug Type: Semaphore related
 Operating System: win32 only
 PHP Version:  5.0.4, 4.3.11
 Assigned To:  iliaa


Previous Comments:


[2005-05-19 23:33:39] joe at bs0 dot com

patch:http://www.bs0.com/~joe/php/tsrm/tsrm_win32.diff
complete: http://www.bs0.com/~joe/php/tsrm/tsrm_win32.c
changes:  http://www.bs0.com/~joe/php/tsrm/changes.txt



[2005-05-18 14:29:34] [EMAIL PROTECTED]

Put a patch on the web, and provide the URL here please. (And if you
can, provide a summary why it was wrong and how you fixed it).



[2005-05-15 02:34:02] joe at bs0 dot com

as short as I can make it:

?php
$toWrite = 'test string';   
$shm_len = strlen($toWrite);

$shm_id = shmop_open(0xff3, c, 0644, $shm_len);

shmop_write($shm_id, $toWrite, 0);
shmop_close($shm_id);

$shm_id = shmop_open(0xff3, a, 0, 0); 
$data = shmop_read($shm_id, 0, $shm_len);   
shmop_close($shm_id);

$shm_id = shmop_open(0xff3, w, 0, 0); 

if (!shmop_delete($shm_id)) {
echo Couldn't mark shared memory block for deletion.br/;
}
else {
echo shared memory block marked for deletion.br/;   
}

shmop_close($shm_id);
echo 'block closed.br/';

$shm_id = shmop_open(0xff3, a, 0, 0); 

if($shm_id) {
$data = shmop_read($shm_id, 0, $shm_len);   
shmop_close($shm_id);   

echo 'ERROR: Previously deleted block able to be opened.br/';
echo 'Data read : ' . $data . '';
}
else {
echo 'Could not open previously deleted block.br/';
}
?



[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=33011edit=1