public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Sukadev Bhattiprolu <sukadev@us.ibm.com>,
	Jiri Slaby <jirislaby@gmail.com>, Pavel Machek <pavel@ucw.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org,
	Oleg Nesterov <oleg@tv-sign.ru>
Subject: Re: 2.6.21-rc4-mm1: freezing of processes broken
Date: Wed, 21 Mar 2007 14:13:54 +1100	[thread overview]
Message-ID: <1174446834.6665.3.camel@nigel.suspend2.net> (raw)
In-Reply-To: <m1lkhre6f5.fsf@ebiederm.dsl.xmission.com>

Hi.

On Tue, 2007-03-20 at 19:23 -0600, Eric W. Biederman wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> writes:
> 
> > On Tuesday, 20 March 2007 22:06, Rafael J. Wysocki wrote:
> >> On Tuesday, 20 March 2007 21:58, Jiri Slaby wrote:
> >> > Rafael J. Wysocki napsal(a):
> >> > > Actually, the problem is 100% reproducible on my system too and I doubt
> > it's
> >> > > caused by the recent freezer patches.
> >> > 
> >> > I don't know what exactly do you mean by recent, but 2.6.21-rc3-mm2 works
> >> > for me.
> >> 
> >> Thanks for the confirmation.
> >> 
> >> The patches I was talking about had already been in 2.6.21-rc3-mm2, so the
> >> reason of this failure must be different.
> >
> > Bisection shows that the freezing of processes has been broken by one of the
> > patches:
> >
> > remove-the-likelypid-check-in-copy_process.patch
> 
> Grr.  Oleg's review of remove-the-likelypid-check-in-copy-process
> showed it to be questionable (and it was just an optimization)
> so we can get rid of that one easily. 
> 
> Although all it did that was really questionable was add
> the idle process to the global process list and bump a process
> count when we forked the idle process.  Not dramatically dangerous
> things.
> 
> > use-task_pgrp-task_session-in-copy_process.patch
> 
> As I recall that patch was pretty trivial, and shouldn't have
> anything to do with the freezer.   The process freezer doesn't care
> about pids does it?

Could the freezer code be trying to freeze the idle thread as a result?

Regards,

Nigel

  parent reply	other threads:[~2007-03-21  3:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070319205623.299d0378.akpm@linux-foundation.org>
2007-03-20 14:31 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 16:09   ` 2.6.21-rc4-mm1 Andrew Morton
2007-03-20 18:38     ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 19:40       ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 19:56         ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 20:13           ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 20:21             ` 2.6.21-rc4-mm1 Pavel Machek
2007-03-20 20:58               ` 2.6.21-rc4-mm1 Rafael J. Wysocki
2007-03-20 20:58                 ` 2.6.21-rc4-mm1 Jiri Slaby
2007-03-20 21:06                   ` 2.6.21-rc4-mm1 Rafael J. Wysocki
2007-03-21  0:49                     ` 2.6.21-rc4-mm1: freezing of processes broken Rafael J. Wysocki
2007-03-21  1:23                       ` Eric W. Biederman
2007-03-21  2:47                         ` sukadev
2007-03-21  3:13                         ` Nigel Cunningham [this message]
2007-03-21 14:23                           ` Oleg Nesterov
2007-03-21 14:45                             ` Rafael J. Wysocki
2007-03-21 16:20                               ` Andrew Morton
2007-03-21 16:55                                 ` Oleg Nesterov
2007-03-21 17:08                                   ` Andrew Morton
2007-03-21 18:07                                     ` [linux-pm] " sukadev
2007-03-21 18:16                                       ` Eric W. Biederman
2007-03-21 18:23                                         ` sukadev
2007-03-21 17:15                                   ` Oleg Nesterov
2007-03-21 12:08                         ` Rafael J. Wysocki
2007-03-20 20:12         ` 2.6.21-rc4-mm1 Rafael J. Wysocki

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=1174446834.6665.3.camel@nigel.suspend2.net \
    --to=nigel@nigel.suspend2.net \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=oleg@tv-sign.ru \
    --cc=pavel@ucw.cz \
    --cc=sukadev@us.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox