Bug 368791

Summary: unhandled amd64-linux syscall: 167 (swapon)
Product: [Developer tools] valgrind Reporter: Michael Yuniverg <umishko>
Component: generalAssignee: Julian Seward <jseward>
Status: REPORTED ---    
Severity: normal CC: mark, tom
Priority: NOR    
Version: 3.11.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:

Description Michael Yuniverg 2016-09-14 08:14:07 UTC 
as you asked reporting:
 Warning: noted but unhandled ioctl 0x4c01 with no size/direction hints.
(1) ==1149==    This could cause spurious value errors to appear.
(1) ==1149==    See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper.
(1) --1149-- WARNING: unhandled amd64-linux syscall: 167
(1) --1149-- You may be able to write your own handler.
(1) --1149-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
(1) --1149-- Nevertheless we consider this a bug.  Please report
(1) --1149-- it at http://valgrind.org/support/bug_reports.html.
(1) --1149-- WARNING: unhandled amd64-linux syscall: 167
(1) --1149-- You may be able to write your own handler.
(1) --1149-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
(1) --1149-- Nevertheless we consider this a bug.  Please report
(1) --1149-- it at http://valgrind.org/support/bug_reports.html.
Comment 1 Tom Hughes 2016-09-14 09:03:31 UTC 
What platform (OS/architecture) is this?
Comment 2 Mark Wielaard 2016-09-14 11:05:17 UTC 
amd64-linux syscall 167 is swapon for which valgrind only has an implementation for mip64, but no other arches apparently.
Comment 3 Julian Seward 2016-09-15 10:44:27 UTC 
Hmm, we should pull those wrappers about of being mips64-linux specific
bucket and make them linux-general instead.  Also it looks like they are missing
a PRE_MEM_RASCIIZ call on the path arguments, assuming it's a normal zero
terminated C string.
Comment 4 Julian Seward 2016-09-15 10:45:06 UTC 
s/about of being/out of the