From: alan@lxorguk.ukuu.org.uk (Alan Cox)
To: andrea@e-mind.com
Cc: Zlatko.Calusic@CARNet.hr, sct@redhat.com, torvalds@transmeta.com,
linux-mm@kvack.org, linux-kernel@vger.rutgers.edu
Subject: Re: BUG: deadlock in swap lockmap handling
Date: Mon, 18 Jan 1999 22:24:38 +0000 (GMT) [thread overview]
Message-ID: <m102N67-0007U1C@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.3.96.990118203741.9904A-100000@laser.bogus> from "Andrea Arcangeli" at Jan 18, 99 09:26:05 pm
> I think it will not harm too much because the window is not too big (but
> not small) and because usually one of the process not yet deadlocked will
> generate IO and will wakeup also the deadlocked process at I/O
> completation time. A very lazy ;) but at the same time obviosly right
Take it from me - the scenario you give will cause deadlocks and problems.
There were other "generating an I/O would have cleaned up" type problems in
2.0.x < .35/6. They caused a lot of grief with installers where that
I/O assumption is not true. Another classic case is large fsck's during
boot up.
So its not just a trivial irrelevant fix.
--
This is a majordomo managed list. To unsubscribe, send a message with
the body 'unsubscribe linux-mm me@address' to: majordomo@kvack.org
next prev parent reply other threads:[~1999-01-18 21:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-18 15:12 Removing swap lockmap Zlatko Calusic
1999-01-18 20:26 ` Andrea Arcangeli
1999-01-18 22:24 ` Alan Cox [this message]
1999-01-18 21:46 ` Stephen C. Tweedie
1999-01-19 1:33 ` Zlatko Calusic
1999-01-19 0:34 ` Eric W. Biederman
1999-01-19 1:37 ` Zlatko Calusic
1999-01-19 18:15 ` Andrea Arcangeli
1999-01-20 17:09 ` Stephen C. Tweedie
1999-01-20 18:14 ` Zlatko Calusic
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=m102N67-0007U1C@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Zlatko.Calusic@CARNet.hr \
--cc=andrea@e-mind.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.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 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.