All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.17-mm3: swsusp fails when process is debugged by ptrace
Date: Wed, 28 Jun 2006 14:52:32 -0700	[thread overview]
Message-ID: <44A2FA20.3020809@goop.org> (raw)
In-Reply-To: <20060628212616.GB30373@elf.ucw.cz>

Pavel Machek wrote:
> Does it also happen when you do strace? ...I remember trying to solve
> that, but 2.6.17-mm3 is very recent...?

I could suspend while running "strace sleep 100" without any problem.

I think the issue is when the process is blocked in T state,
freeze_process() tries to kick the process with signal_wake_up(p, /*
resume=0 */ 0), but with resume=0 it will only wake processes in
TASK_INTERRUPTIBLE state.  With resume=1, it will also kick STOPPED and
TRACED processes.  I also tried suspending while I had a process in T
state caused by kill -STOP, and that worked, so some part of the puzzle
is still missing.

I noticed that when I ran sleep 100 under strace over the suspend/resume
cycle, its nanosleep() syscall was interrupted and not restarted.

    J

  reply	other threads:[~2006-06-28 21:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 17:17 2.6.17-mm3: swsusp fails when process is debugged by ptrace Jeremy Fitzhardinge
2006-06-28 21:26 ` Pavel Machek
2006-06-28 21:52   ` Jeremy Fitzhardinge [this message]
2006-07-03 21:33     ` Pavel Machek
2006-07-03 21:54       ` Jeremy Fitzhardinge

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=44A2FA20.3020809@goop.org \
    --to=jeremy@goop.org \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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.