From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
Patrick Mochel <mochel@digitalimplant.org>,
akpm@zip.com.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: -mm swsusp: do not default to platform/firmware
Date: Thu, 29 Jul 2004 10:30:26 +1000 [thread overview]
Message-ID: <1091061026.8873.78.camel@laptop.cunninghams> (raw)
In-Reply-To: <20040728234352.GA14319@elf.ucw.cz>
Hi.
On Thu, 2004-07-29 at 09:43, Pavel Machek wrote:
> +I did found some kernel threads don't do it, and they don't freeze, and
"I found... threads that don't..."
> +so the system can't sleep. Is this a known behavior?
> +
> +A: All such kernel threads need to be fixed, one by one. Select place
> +where it is safe to be frozen (no kernel semaphores should be held at
> +that point and it must be safe to sleep there), and add:
> +
> + if (current->flags & PF_FREEZE)
> + refrigerator(PF_FREEZE);
> +
Perhaps you should also add.
If the thread is needed for writing the image to storage, you should
instead set the PF_NOFREEZE process flag when creating the thread.
Regards,
Nigel
next prev parent reply other threads:[~2004-07-29 0:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-28 22:24 Pavel Machek
2004-07-28 23:14 ` Andrew Morton
2004-07-28 23:39 ` Pavel Machek
2004-07-28 23:43 ` Pavel Machek
2004-07-29 0:30 ` Nigel Cunningham [this message]
2004-07-29 7:39 ` Pavel Machek
2004-07-29 7:52 ` Nigel Cunningham
2004-08-02 6:15 ` Patrick Mochel
2004-08-02 15:30 ` Kevin Fenzi
2004-08-03 11:28 ` Karol Kozimor
2004-08-09 19:44 ` Pavel Machek
2004-08-08 17:13 ` Pavel Machek
2004-07-29 5:19 Li, Shaohua
2004-07-29 7:38 ` Pavel Machek
2004-07-29 8:03 ` Nigel Cunningham
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=1091061026.8873.78.camel@laptop.cunninghams \
--to=ncunningham@linuxmail.org \
--cc=akpm@osdl.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@digitalimplant.org \
--cc=pavel@ucw.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®