As I recently learned making a kernel area B_READ_AREA/B_WRITE_AREA makes
it readable/writable for all userland apps. This is not what we want here. We want to make the area cloneable for the registrar and hence use the new flag B_USER_CLONEABLE_AREA. But there seems to be a bug that causes strange things to happen, when using that flag only, therefore we go with all of them until it is fixed. git-svn-id: file:///srv/svn/repos/haiku/trunk/current@11046 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
parent
6e53f60e2c
commit
aa50545364
@ -150,7 +150,8 @@ MessagingArea::Create(sem_id lockSem, sem_id counterSem)
|
||||
// create the area
|
||||
area->fID = create_area("messaging", (void**)&area->fHeader,
|
||||
B_ANY_KERNEL_ADDRESS, kMessagingAreaSize, B_FULL_LOCK,
|
||||
B_READ_AREA | B_WRITE_AREA);
|
||||
// B_USER_CLONEABLE_AREA);
|
||||
B_READ_AREA | B_WRITE_AREA | B_USER_CLONEABLE_AREA);
|
||||
if (area->fID < 0) {
|
||||
delete area;
|
||||
return NULL;
|
||||
|
Loading…
Reference in New Issue
Block a user