×
Namespaces

Variants
Actions
(Difference between revisions)

Archived:Binary-incompatible change in Open C to require proper permission checks for creating IPC resources (Known Issue)

From Nokia Developer Wiki
Jump to: navigation, search
hamishwillee (Talk | contribs)
m (Hamishwillee - Bot change of template (Template:KnowledgeBase) - now using Template:ArticleMetaData)
debjit.roy (Talk | contribs)
(Debjit.roy -)
Line 1: Line 1:
[[Category:Symbian C++]]
+
[[Category:Symbian C++]][[Category:Open C/C++]][[Category:Known Issue]][[Category:S60 3rd Edition]]
 
{{KBKI}}
 
{{KBKI}}
 
__NOTOC__
 
__NOTOC__
Line 20: Line 20:
 
|author=[[User:Technical writer 1]]
 
|author=[[User:Technical writer 1]]
 
}}
 
}}
 
+
{{Archived|timestamp=20120223111221|user=roy.debjit| }}
 
==Overview==
 
==Overview==
 
To improve the performance and better adhere to POSIX standards, the next release of Open C will undergo some changes in the architecture. Some of the changes will also affect the binary compatibility with previous releases.
 
To improve the performance and better adhere to POSIX standards, the next release of Open C will undergo some changes in the architecture. Some of the changes will also affect the binary compatibility with previous releases.
Line 35: Line 35:
  
 
==Solution==
 
==Solution==
Starting from the next Open C release, <tt>IPC_CREAT</tt> has to be OR-ed with <tt>READ (0400)</tt> or/and <tt>WRITE (0200)</tt> permission.[[Category:Open C/C++]][[Category:Known Issue]][[Category:S60 3rd Edition]]
+
Starting from the next Open C release, <tt>IPC_CREAT</tt> has to be OR-ed with <tt>READ (0400)</tt> or/and <tt>WRITE (0200)</tt> permission.

Revision as of 14:12, 23 February 2012

Template:KBKI


Article Metadata
Tested with
Devices(s): All (S60 3rd Edition devices)
Compatibility
Platform(s): S60 3rd Edition
Symbian
S60 3rd Edition (initial release)
Article
Created: User:Technical writer 1 (20 Aug 2008)
Last edited: debjit.roy (23 Feb 2012)

Archived.pngArchived: 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}}.

Overview

To improve the performance and better adhere to POSIX standards, the next release of Open C will undergo some changes in the architecture. Some of the changes will also affect the binary compatibility with previous releases.

Description

Proper permissions must now be defined when creating IPC (inter-process communication) resources (shm, semaphore</tt, and <tt>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.

141 page views in the last 30 days.
×