Previously, I was calling setfsuid(-1) to check if the
previous call had succeeded, since this syscall will
always return the current fsuid, whether the syscall
itself succeeded or not. There's no way to check
other than calling setfsuid again, since there's no
getfsuid.
The expectation was that setfsuid(-1) will always fail
and not affect the fsuid, effectively acting as getfsuid,
but it appears that on SLC6 it succeeds, setting the
fsuid to.. 4294967295. On Fedora 26 it fails as expected,
I have no idea why there's a difference.
Instead, let's use setfsuid(pFsUid) again, just to
check if the previous call succeeded.
You can view, comment on, or merge this pull request online at:
https://github.com/xrootd/xrootd/pull/605
-- Commit Summary --
* [XrdCl] Fix error checking when setting sec.uid, sec.gid
-- File Changes --
M src/XrdCl/XrdClUtils.hh (4)
-- Patch Links --
https://github.com/xrootd/xrootd/pull/605.patch
https://github.com/xrootd/xrootd/pull/605.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/xrootd/xrootd/pull/605
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
