valgrind-users

[Valgrind-users] setns syscall with valgrind

[Himanshu S <mai...@gm...>]

Hello,
I started using valgrind for our code and it is a great tool. In our code
we use setns system call. It seems like valgrind version (3.8.1). It seems
like this syscall is not handled.


--2726-- WARNING: unhandled syscall: 308
--2726-- You may be able to write your own handler.
--2726-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--2726-- Nevertheless we consider this a bug.  Please report
--2726-- it at http://valgrind.org/support/bug_reports.html.

I wanted to check if anyone knows about this issue being fixed or if anyone
has a patch that works?

Thanks in advance
-Himanshu

Re: [Valgrind-users] setns syscall with valgrind

[John R. <jr...@Bi...>]

> In our code we use setns system call. [In] valgrind version (3.8.1), it seems like this syscall is not handled. 
> 
> 
> --2726-- WARNING: unhandled syscall: 308
> --2726-- You may be able to write your own handler.
> --2726-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
> --2726-- Nevertheless we consider this a bug.  Please report
> --2726-- it at http://valgrind.org/support/bug_reports.html.


Version 3.9.0 was released about 7 or 8 months ago.  Why not upgrade?

You should tell us which hardware architecture and which operating system.

Because the setns system call:
	int setns(int fd, int nstype);
does not reference memory, then setns is a no-operation as far as memcheck is concerned.
Write an empty subroutine and put its address into the table:
	static SyscallTableEntry syscall_table[] = { ... };
Then submit your patch at the indicated URL.

Re: [Valgrind-users] setns syscall with valgrind

[Himanshu S <mai...@gm...>]

John, Thanks for the response. We are using 64-bit x86 Linux. As such setns
switches the network name space context to the one where the 'fd' in the
argument is referring. I will try your suggestion and let you know.


On Fri, May 23, 2014 at 6:14 PM, John Reiser <jr...@bi...> wrote:

> > In our code we use setns system call. [In] valgrind version (3.8.1), it
> seems like this syscall is not handled.
> >
> >
> > --2726-- WARNING: unhandled syscall: 308
> > --2726-- You may be able to write your own handler.
> > --2726-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
> > --2726-- Nevertheless we consider this a bug.  Please report
> > --2726-- it at http://valgrind.org/support/bug_reports.html.
>
>
> Version 3.9.0 was released about 7 or 8 months ago.  Why not upgrade?
>
> You should tell us which hardware architecture and which operating system.
>
> Because the setns system call:
>         int setns(int fd, int nstype);
> does not reference memory, then setns is a no-operation as far as memcheck
> is concerned.
> Write an empty subroutine and put its address into the table:
>         static SyscallTableEntry syscall_table[] = { ... };
> Then submit your patch at the indicated URL.
>
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.
> Get unparalleled scalability from the best Selenium testing platform
> available
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Valgrind-users mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-users
>