Bug 68896 - mm doesn't change ownership properly of SysV semaphores
mm doesn't change ownership properly of SysV semaphores
Product: Red Hat Public Beta
Classification: Retired
Component: mm (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brian Brock
Depends On: 68895
  Show dependency treegraph
Reported: 2002-07-15 15:56 EDT by Jonathan Kamens
Modified: 2007-04-18 12:44 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-07-31 04:51:38 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
patch to set perms of semaphores in mm (822 bytes, patch)
2002-07-15 15:57 EDT, Jonathan Kamens
no flags Details | Diff

  None (edit)
Description Jonathan Kamens 2002-07-15 15:56:56 EDT
When mm is told to change the ownership or modes of a shared memory object, it
doesn't properly update the ownership or mode of semaphores (assuming that it is
compiled with semaphores enabled).  I'll attach a patch.
Comment 1 Jonathan Kamens 2002-07-15 15:57:36 EDT
Created attachment 65464 [details]
patch to set perms of semaphores in mm
Comment 2 Nalin Dahyabhai 2002-07-24 15:05:48 EDT
Fixing for 1.1.3-8 and later.
Comment 3 Jonathan Kamens 2002-07-26 10:15:10 EDT
The author of mm pointed out a problem in my patch.  When I wrote "i <=
sizeof(sems)/sizeof(*sems)", the "<=" should have been "<".  Please fix this if
you retained the bug when integrating my patch into your package.

Also, he said that my fix will be in mm 1.2.0, although I don't know if/when
that'll be released.
Comment 4 Mark J. Cox 2002-07-31 04:51:38 EDT
An errata has been issued which should help the problem described in this bug report. 
This report is therefore being closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files, please follow the link below. You may reopen 
this bug report if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.