Archived:Binary-incompatible change in Open C to require proper permission checks for creating IPC resources (Known Issue)
Latest revision as of 10:00, 15 June 2012
Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.
This known issue outlines binary incompatible changes to the Open C architecture in the next release. These changes will improve the performance and better adhere to POSIX standards.
Article Metadata
Tested with
Devices(s): All (S60 3rd Edition devices)
Compatibility
Platform(s): S60 3rd Edition
Article
Created: User:Technical writer 1
(20 Aug 2008)
Last edited: hamishwillee
(15 Jun 2012)
Description
Proper permissions must now be defined when creating IPC (inter-process communication) resources (shm, semaphore, and msgqueue). The flag argument (value) can no longer be just IPC_CREAT. Specifying only IPC_CREAT means that the IPC resource is created with absolutely no permissions, and will result in EACCESS error.
How to reproduce
int msgid;
struct msqid_ds buf = {0};
msgid = msgget(1000, 512); /* returns with errno = 13 */
Solution
Starting from the next Open C release, IPC_CREAT has to be OR-ed with READ (0400) or/and WRITE (0200) permission.
