summaryrefslogtreecommitdiff
path: root/lua_scripts
diff options
context:
space:
mode:
authorLauri Aarnio <Lauri.Aarnio@iki.fi>2008-11-26 20:28:22 +0200
committerLauri Leukkunen <lle@rahina.org>2008-12-07 04:32:47 +0200
commit469f3992cd8764b10450391d79ebb9ec0aeff546 (patch)
treea8b18d0f9220d365189f5d9e5e98ed8a266f2f8f /lua_scripts
parent414f63552e0a36483781c257c20e0920b9fd1066 (diff)
Workaround for a system call bug in older "libattr" libraries of ARM targets
- Older "libattr" libraries for ARM use an incorrect format for some system calls; Maemo's patched qemu now has workaround for that. Now sb2 detects if the selected qemu knows about this "libattr hack" and enables it if possible.
Diffstat (limited to 'lua_scripts')
-rw-r--r--lua_scripts/argvenvp.lua10
1 files changed, 10 insertions, 0 deletions
diff --git a/lua_scripts/argvenvp.lua b/lua_scripts/argvenvp.lua
index 4bde158..23caca2 100644
--- a/lua_scripts/argvenvp.lua
+++ b/lua_scripts/argvenvp.lua
@@ -476,6 +476,16 @@ function sb_execve_postprocess_cpu_transparency_executable(rule, exec_policy,
new_argv[6] = argv[1]
end
+ if conf_cputransparency_qemu_has_libattr_hack_flag then
+ -- For ARM emulation:
+ -- a nasty bug exists in some older libattr library
+ -- version (e.g. it causes "ls -l" to crash), this
+ -- flag enables a hack in Qemu which makes
+ -- libattr to work correctly even if it uses incorrect
+ -- system call format.
+ table.insert(new_argv, "-libattr-hack")
+ end
+
if conf_cputransparency_qemu_has_env_control_flags then
for i = 1, #envp do
-- drop LD_TRACE_ from target environment