Bug 369033

Summary:	WARNING: unhandled amd64-linux syscall: 139 (sysfs)
Product:	[Developer tools] valgrind	Reporter:	Marcin Juszkiewicz <marcin>
Component:	general	Assignee:	Julian Seward <jseward>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	mark, tom
Priority:	NOR
Version First Reported In:	3.11.0
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Marcin Juszkiewicz 2016-09-19 06:49:24 UTC

<<<test_start>>>
tag=sysfs01_valgrind_memory_leak_check stime=1474225812
cmdline=" valgrind -q --leak-check=full --trace-children=yes sysfs01"
contacts=""
analysis=exit
<<<test_output>>>
--26537-- WARNING: unhandled amd64-linux syscall: 139
--26537-- You may be able to write your own handler.
--26537-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--26537-- Nevertheless we consider this a bug.  Please report
--26537-- it at http://valgrind.org/support/bug_reports.html.
sysfs01     1  TCONF  :  sysfs01.c:94: syscall(139) __NR_sysfs not supported on your arch
sysfs01     2  TCONF  :  sysfs01.c:94: Remaining cases not appropriate for configuration
<<<execution_status>>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=32 corefile=no
cutime=61 cstime=1
<<<test_end>>>


Reproducible: Always

Comment 1 Marcin Juszkiewicz 2018-04-30 08:07:14 UTC

Can we close it? IIRC it was merged into valgrind.

Comment 2 Tom Hughes 2018-04-30 09:56:28 UTC

I see no sign that this has been added.

Comment 3 Mark Wielaard 2021-10-04 09:13:50 UTC

This has only been implemented for Solaris.

NOTES
       This  System-V  derived system call is obsolete; don't use it.  On sys‐
       tems  with  /proc,  the  same   information   can   be   obtained   via
       /proc/filesystems; use that interface instead.

Comment 4 Marcin Juszkiewicz 2021-10-04 18:03:21 UTC

As sysfs() is obsolete there is no sense in keeping this bug open.