From: "David S. Miller" <davem@redhat.com>
To: kasperd@daimi.au.dk
Cc: manfred@colorfullife.com, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org
Subject: Re: [TRIVIAL] Warn users about machines with non-working WP bit
Date: Tue, 06 Aug 2002 07:05:35 -0700 (PDT) [thread overview]
Message-ID: <20020806.070535.24871584.davem@redhat.com> (raw)
In-Reply-To: <3D4FDA23.90CAB62F@daimi.au.dk>
From: Kasper Dupont <kasperd@daimi.au.dk>
Date: Tue, 06 Aug 2002 16:16:03 +0200
"David S. Miller" wrote:
> What if we have to sleep and page in some memory from disk?
>
> Your idea could lead to deadlock in a multi-threaded app.
Why? The page should eventually get into memory from the disk,
at this point the process doing the copy can continue, and
when it finishes the other processes gets waked up. While the
copy_to_user is in progress all the processes witht this mm
should be in noninterruptible sleep. The sleeping procces
doesn't need to do anything to get the page into memory, so I
cannot see the problem.
What if the other thread we freeze is holding a lock we
need in order to get the page from disk?
next prev parent reply other threads:[~2002-08-06 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 9:17 [TRIVIAL] Warn users about machines with non-working WP bit Manfred Spraul
2002-08-06 9:28 ` David S. Miller
2002-08-06 9:42 ` Manfred Spraul
2001-08-20 20:03 ` Pavel Machek
2002-08-06 14:03 ` Kasper Dupont
2002-08-06 13:56 ` David S. Miller
2002-08-06 14:16 ` Kasper Dupont
2002-08-06 14:05 ` David S. Miller [this message]
2002-08-06 14:27 ` Kasper Dupont
2002-08-06 14:36 ` Manfred Spraul
2001-08-20 20:06 ` Pavel Machek
2002-08-19 22:04 ` Alan Cox
2002-08-06 15:11 ` Kasper Dupont
2002-08-06 16:38 ` Willy Tarreau
2002-08-06 16:45 ` Zwane Mwaikambo
-- strict thread matches above, loose matches on Subject: below --
2002-08-06 3:49 Rusty Trivial Russell
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=20020806.070535.24871584.davem@redhat.com \
--to=davem@redhat.com \
--cc=kasperd@daimi.au.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=rusty@rustcorp.com.au \
/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