From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Hugh Dickins <hugh@veritas.com>
Cc: Lukas Hejtmanek <xhejtman@mail.muni.cz>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: Swapoff inifinite loops on 2.6.10-bk (was: .6.10-bk8 swapoff after resume)
Date: Sat, 08 Jan 2005 17:23:34 +0100 [thread overview]
Message-ID: <1105201414.4514.2.camel@tux.rsn.bth.se> (raw)
In-Reply-To: <Pine.LNX.4.44.0501081547260.2688-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Sat, 2005-01-08 at 16:00 +0000, Hugh Dickins wrote:
> You're right, and yes, I could then reproduce it. Looks like I'd only
> been testing on 3levels (HIGHMEM64G), and this only happens on 2levels.
>
> Patch below, please verify it fixes your problems. And please, could
> someone else check I haven't screwed up swapoff on 4levels (x86_64)?
> From the likeness of the code at all levels I'd expect it to be fine,
> but there's nothing like a real test - thanks...
The patch fixes the problem completely here.
swapoff after running the memory hog works as expected.
and swapoff after suspend to disk and resume also works fine.
Thanks for tracking this down and fixing it.
--
/Martin
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-01-08 16:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 13:47 2.6.10-bk8 swapoff after resume Lukas Hejtmanek
2005-01-06 21:14 ` Swapoff inifinite loops on 2.6.10-bk (was: .6.10-bk8 swapoff after resume) Martin Josefsson
2005-01-06 22:00 ` Hugh Dickins
2005-01-07 6:53 ` Martin Josefsson
2005-01-08 16:00 ` Hugh Dickins
2005-01-08 16:23 ` Martin Josefsson [this message]
2005-01-08 19:57 ` Andrew Morton
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=1105201414.4514.2.camel@tux.rsn.bth.se \
--to=gandalf@wlug.westbo.se \
--cc=akpm@osdl.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xhejtman@mail.muni.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;
as well as URLs for NNTP newsgroup(s).