* [Linux-ia64] Shared memory
@ 2000-05-18 19:25 roneng
2000-05-24 18:32 ` Christoph Rohland
0 siblings, 1 reply; 2+ messages in thread
From: roneng @ 2000-05-18 19:25 UTC (permalink / raw)
To: linux-ia64
Hi,
Has anyone had a problem using the shmctl function to change the access
mode of a shared memory
block?
What I am doing is allocating shared memory using mode 666, and writing to
it, then I use shmctl to change its
mode to 600, switch to another userid using su, and try and read from the
shared memory block. on ia32 linux
I get an permission denied error, on ia64 with the latest turbolinux kernel
and glibc i can read from that memory
block.
Thank you,
Ronen Grosman
- Phone: Internal:778-4478 External: (416)-448-4478 Fax:
(416)448-4414
- e-mail roneng@ca.ibm.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Linux-ia64] Shared memory
2000-05-18 19:25 [Linux-ia64] Shared memory roneng
@ 2000-05-24 18:32 ` Christoph Rohland
0 siblings, 0 replies; 2+ messages in thread
From: Christoph Rohland @ 2000-05-24 18:32 UTC (permalink / raw)
To: linux-ia64
Hi Ronen,
roneng@ca.ibm.com writes:
> Has anyone had a problem using the shmctl function to change the access
> mode of a shared memory
> block?
>
> What I am doing is allocating shared memory using mode 666, and writing to
> it, then I use shmctl to change its
> mode to 600, switch to another userid using su, and try and read from the
> shared memory block. on ia32 linux
> I get an permission denied error, on ia64 with the latest turbolinux kernel
> and glibc i can read from that memory
> block.
That's an arch independent bug in the shm code. I will try to make a
fix beginning next week.
Thanks for spotting this,
Christoph
--
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2000-05-24 18:32 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-05-18 19:25 [Linux-ia64] Shared memory roneng
2000-05-24 18:32 ` Christoph Rohland
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox