This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[PATCH] Fix mkdtemp() umask issue
- From: Mark McLoughlin <markmc at redhat dot com>
- To: systemtap at sources dot redhat dot com
- Cc: Mark McLoughlin <markmc at redhat dot com>
- Date: Mon, 17 Dec 2007 16:47:59 +0000
- Subject: [PATCH] Fix mkdtemp() umask issue
Even though the mkdtemp() man page indicates that the
directory will be created with always 0700 permissions,
it is actually affected by the process's umask.
So, if you run stap with an unusual umask it can end
up creating the temp dir with permissions that
staprun can't handle e.g.:
$> rpm -q systemtap
systemtap-0.6-1.fc9
$> umask 0122
$> stap -e 'probe begin { println("foo") exit() }'
ERROR: Error opening '/tmp/stapV4pBIb/stap_725b9bc541cef2618a5ccbc58bb64d15_287.ko': Permission denied
Obvious solution is to briefly set the umask to zero
in stap so as to ensure 0700 permissions.
Signed-off-by: Mark McLoughlin <markmc@redhat.com>
---
main.cxx | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/main.cxx b/main.cxx
index 1880436..556b30f 100644
--- a/main.cxx
+++ b/main.cxx
@@ -521,7 +521,9 @@ main (int argc, char * const argv [])
string stapdir = "/stapXXXXXX";
string tmpdirt = tmpdir_env + stapdir;
+ mode_t mask = umask(0);
const char* tmpdir = mkdtemp((char *)tmpdirt.c_str());
+ umask(mask);
if (! tmpdir)
{
const char* e = strerror (errno);
--
1.5.3.3