Openwall GNU/*/Linux - a small security-enhanced Linux distro for servers
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 19 Jul 2012 22:04:05 +0400
From: "Dmitry V. Levin" <ldv@...linux.org>
To: owl-dev@...ts.openwall.com
Subject: Re: strace with restart_syscall output (was: status of 2.6.32-based kernel)

On Thu, Jul 19, 2012 at 08:43:07PM +0400, Vasily Kulikov wrote:
> On Thu, Jul 19, 2012 at 20:22 +0400, Dmitry V. Levin wrote:
> > On Thu, Jul 19, 2012 at 08:13:05PM +0400, Vasily Kulikov wrote:
> > [...]
> > > I've tried some tools a bit like modprobe, ip, nmap, ping, brctl --
> > > everything works, except strace.  It shows the same line for every
> > > syscall:
> > > 
> > > restart_syscall(<... resuming interrupted call ...>) = 12
> > > restart_syscall(<... resuming interrupted call ...>) = 0
> > > restart_syscall(<... resuming interrupted call ...>) = 0
> > > ...
> > 
> > Is it x86 or x86-64?  __NR_restart_syscall is 0 on x86.
> 
> It is x86

Then most likely it fails to fetch syscall numbers, and if it is the case,
then it also fails to recognize the failure.
Let's have a look at "strace -d /bin/true" output, it may give a clue.


-- 
ldv

[ CONTENT OF TYPE application/pgp-signature SKIPPED ]

Powered by blists - more mailing lists

Your e-mail address:

Powered by Openwall GNU/*/Linux - Powered by OpenVZ