From: Hugh Dickins <hugh@veritas.com>
To: Dave McCracken <dmccr@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH 2.5.42-mm3] Fix mremap for shared page tables
Date: Wed, 16 Oct 2002 16:08:17 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0210161543170.1320-100000@localhost.localdomain> (raw)
In-Reply-To: <291360000.1034721127@baldur.austin.ibm.com>
On Tue, 15 Oct 2002, Dave McCracken wrote:
>
> Hugh Dickens was right. mremap was broken wrt shared page tables.
i
Sorry, Dave, I only mentioned mremap as one _example_. You have
changed the locking rules for ptes in page tables in two or three
sources, but there's a number more which need to be updated too.
Please don't ask me to list which, it's a matter of looking at all
the uses of ->page_table_lock and whether those places need to be
changed to fit the new locking scheme - some of the uses are quite
irrelevant, some may be obscure, some may be historic, some must
be changed.
I wouldn't mind if it was just broken wrt shared page tables,
CONFIG_SHAREPTE is easily made experimental. But the locking rules
have (rightly) been changed in all cases, so -mm tree is now unsafe.
A stopgap measure might be to hold on to page_table_lock for as
long as before, then fix sources up piecemeal - but that approach
would still leave CONFIG_SHAREPTE y broken for a while.
Let me say again, that I have _not_ actually observed any problem
yet: we're talking about races and correctness, I don't mean to be
alarmist.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2002-10-16 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 22:32 Dave McCracken
2002-10-16 15:08 ` Hugh Dickins [this message]
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=Pine.LNX.4.44.0210161543170.1320-100000@localhost.localdomain \
--to=hugh@veritas.com \
--cc=akpm@digeo.com \
--cc=dmccr@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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