You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When user created semaphore with mode 777, the actual mode of it may
not be expected because of umask. In this case, another non-root user
calling sem_open will get error EACCES then mSemLock is 0, which can
cause later segment fault. To avoid this, we directly change the
semaphore file mode to 0666 by chmod and add null check in lock().
Signed-off-by: Hao Yao <hao.yao@intel.com>
0 commit comments