<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>173177</bug_id>
          
          <creation_ts>2008-10-20 06:06:59 +0000</creation_ts>
          <short_desc>[x86_64] WARNING: unhandled syscall: 125/126/179 (capget/capset/quotactl)</short_desc>
          <delta_ts>2009-06-29 09:09:20 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>6</classification_id>
          <classification>Developer tools</classification>
          <product>valgrind</product>
          <component>general</component>
          <version>3.3.1</version>
          <rep_platform>Debian testing</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>0</everconfirmed>
          <reporter name="Kyle Moffett">kyle</reporter>
          <assigned_to name="Julian Seward">jseward</assigned_to>
          <cc>vl</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin></cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>655480</commentid>
    <comment_count>0</comment_count>
    <who name="Kyle Moffett">kyle</who>
    <bug_when>2008-10-20 06:06:59 +0000</bug_when>
    <thetext>While attempting to use valgrind on my x86_64 samba binary, I get the following unhandled syscall warnings:

--00:06:17:34.954 4224-- WARNING: unhandled syscall: 125
==00:06:17:34.954 4224==    at 0x7C79C27: capget (in /usr/lib/debug/libc-2.7.so)
==00:06:17:34.954 4224==    by 0x4031241: cap_get_proc (in /lib/libcap.so.1.10)
==00:06:17:34.954 4224==    by 0x59DEB7: set_process_capability (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x59E06D: set_effective_capability (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x5DCFA3: linux_setlease (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x4AFC5C: vfswrap_linux_setlease (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x5DCD50: linux_set_kernel_oplock (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x5DA586: set_file_oplock (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x4907CA: open_file_ntcreate (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x491529: create_file_unixpath (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x491D7F: create_file (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x783622: reply_ntcreate_and_X (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x4A264D: switch_message (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x4A40F7: smbd_process (in /usr/sbin/smbd)
==00:06:17:34.954 4224==    by 0x471842: main (in /usr/sbin/smbd)
--00:06:17:34.954 4224-- You may be able to write your own handler.
--00:06:17:34.954 4224-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--00:06:17:34.954 4224-- Nevertheless we consider this a bug.  Please report
--00:06:17:34.954 4224-- it at http://valgrind.org/support/bug_reports.html.

--00:06:17:34.963 4224-- WARNING: unhandled syscall: 126
==00:06:17:34.963 4224==    at 0x7C79C57: capset (in /usr/lib/debug/libc-2.7.so)
==00:06:17:34.963 4224==    by 0x403129D: cap_set_proc (in /lib/libcap.so.1.10)
==00:06:17:34.963 4224==    by 0x59E03E: set_process_capability (in /usr/sbin/smbd)
==00:06:17:34.963 4224==    by 0x59E06D: set_effective_capability (in /usr/sbin/smbd)
==00:06:17:34.963 4224==    by 0x5DCFA3: linux_setlease (in /usr/sbin/smbd)
==00:06:17:34.963 4224==    by 0x4AFC5C: vfswrap_linux_setlease (in /usr/sbin/smbd)
==00:06:17:34.963 4224==    by 0x5DCD50: linux_set_kernel_oplock (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x5DA586: set_file_oplock (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x4907CA: open_file_ntcreate (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x491529: create_file_unixpath (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x491D7F: create_file (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x783622: reply_ntcreate_and_X (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x4A264D: switch_message (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x4A40F7: smbd_process (in /usr/sbin/smbd)
==00:06:17:34.964 4224==    by 0x471842: main (in /usr/sbin/smbd)
--00:06:17:34.964 4224-- You may be able to write your own handler.
--00:06:17:34.964 4224-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--00:06:17:34.964 4224-- Nevertheless we consider this a bug.  Please report
--00:06:17:34.964 4224-- it at http://valgrind.org/support/bug_reports.html.

--00:06:17:53.031 4224-- WARNING: unhandled syscall: 179
==00:06:17:53.031 4224==    at 0x7C7A04A: quotactl (in /usr/lib/debug/libc-2.7.so)
==00:06:17:53.031 4224==    by 0x7B2B3B: sys_get_linux_gen_quota (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x7B3480: sys_get_vfs_quota (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x7B1FE5: sys_get_quota (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x7B3EC6: disk_quotas (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x7744CF: sys_disk_free (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x4B076D: vfswrap_disk_free (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x773FD4: get_dfree_info (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x79DE48: call_trans2qfsinfo (in /usr/sbin/smbd)
==00:06:17:53.031 4224==    by 0x7ABF39: handle_trans2 (in /usr/sbin/smbd)
==00:06:17:53.032 4224==    by 0x7ADA47: reply_trans2 (in /usr/sbin/smbd)
==00:06:17:53.032 4224==    by 0x4A264D: switch_message (in /usr/sbin/smbd)
==00:06:17:53.032 4224==    by 0x4A40F7: smbd_process (in /usr/sbin/smbd)
==00:06:17:53.032 4224==    by 0x471842: main (in /usr/sbin/smbd)
--00:06:17:53.032 4224-- You may be able to write your own handler.
--00:06:17:53.032 4224-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--00:06:17:53.032 4224-- Nevertheless we consider this a bug.  Please report
--00:06:17:53.032 4224-- it at http://valgrind.org/support/bug_reports.html.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>657305</commentid>
    <comment_count>1</comment_count>
    <who name="Julian Seward">jseward</who>
    <bug_when>2008-10-26 18:01:03 +0000</bug_when>
    <thetext>sys_capget and sys_capset are already supported in the svn trunk on
amd64-linux (although not in 3.3.1).  That just leaves sys_quotactl.

Could you check out the trunk as described at
http://www.valgrind.org/downloads/repository.html, apply the
patch below, build, and let me know if it works correctly?

Index: coregrind/m_syswrap/syswrap-amd64-linux.c
===================================================================
--- coregrind/m_syswrap/syswrap-amd64-linux.c   (revision 8708)
+++ coregrind/m_syswrap/syswrap-amd64-linux.c   (working copy)
@@ -1229,7 +1229,7 @@
    LINX_(__NR_delete_module,     sys_delete_module),  // 176
    //   (__NR_get_kernel_syms,   sys_ni_syscall),     // 177
    //   (__NR_query_module,      sys_ni_syscall),     // 178
-   //LINX_(__NR_quotactl,          sys_quotactl),       // 179
+   LINX_(__NR_quotactl,          sys_quotactl),       // 179

    //   (__NR_nfsservctl,        sys_nfsservctl),     // 180
    //   (__NR_getpmsg,           sys_ni_syscall),     // 181
</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>658856</commentid>
    <comment_count>2</comment_count>
    <who name="Julian Seward">jseward</who>
    <bug_when>2008-10-30 14:13:46 +0000</bug_when>
    <thetext>Closing this in the absence of further feedback.  Patch above
committed as r8720.  If you do get an opportunity to test it,
I&apos;d appreciate hearing the results.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>783705</commentid>
    <comment_count>3</comment_count>
    <who name="Nicholas Nethercote">njn</who>
    <bug_when>2009-06-29 09:09:20 +0000</bug_when>
    <thetext>*** Bug 154268 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>