All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Houston <jim.houston@attbi.com>
To: "Marco d'Itri" <md@Linux.IT>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.51 nanosleep fails
Date: Wed, 11 Dec 2002 16:05:20 -0500	[thread overview]
Message-ID: <3DF7A890.A688AF54@attbi.com> (raw)

Marco d'Itri wrote:
> nanosleep fails after being interrupted:
>
> [...]
> nanosleep({1, 0},
> [1]+  Stopped                 strace tail -f /var/log/uucp/Log
> md@wonderland:~$ fg
> strace tail -f /var/log/uucp/Log
>  <unfinished ...>
> --- SIGCONT (Continued) ---
> <... nanosleep resumed> 0)              = -1 ENOSYS (Function not implemented)>
>
> This can be reliably reproduced.                                              

Hi Marco, Everyone,

I was able to reproduce this issue.  It happens on all the
kernels I tried including a stock Redhat kernel.  This is just 
an idiosyncrasy of strace. In this case both the strace and
tail are sent a SIGTSTP when they are put into the background.
Its not suprising that this might confuse strace.

I also tried this with a program which just does a long
nanosleep.  Strace still shows a return of ENOSYS but the
program actually gets the correct EINTR.

Jim Houston - Concurrent Computer Corp.

             reply	other threads:[~2002-12-11 20:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-11 21:05 Jim Houston [this message]
2002-12-12 20:57 ` 2.5.51 nanosleep fails Marco d'Itri
  -- strict thread matches above, loose matches on Subject: below --
2002-12-12 22:27 Jim Houston
2002-12-13  1:29 ` Stephen Rothwell
2002-12-12 19:59 Fleischer, Julie N
2002-12-10 23:57 Marco d'Itri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3DF7A890.A688AF54@attbi.com \
    --to=jim.houston@attbi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=md@Linux.IT \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.