From: Ravi <kravi26@yahoo.com>
To: linux-mm@kvack.org, kernelnewbies@nl.linux.org
Subject: BUG_ON in remap_pte_range: Why?
Date: Tue, 20 May 2003 13:27:28 -0700 (PDT) [thread overview]
Message-ID: <20030520202728.42626.qmail@web12308.mail.yahoo.com> (raw)
Hi,
I am looking at the latest mm/memory.c on Bitkeeper.
The comment for remap_pte_range() says "maps a range of
physical memory into the requested pages. the old mappings
are removed". But the code has this check:
BUG_ON(!pte_none(*pte));
Why is it a bug to have a valid PTE when remap_pte_range()
is called? The 2.4 version of this fucntion cleared the
old PTE using ptep_get_and_clear() and then installed
a new one. Why was this changed?
Thanks,
Ravi.
__________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo.
http://search.yahoo.com
--
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/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next reply other threads:[~2003-05-20 20:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 20:27 Ravi [this message]
2003-05-21 4:20 ` Ed L Cashin
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=20030520202728.42626.qmail@web12308.mail.yahoo.com \
--to=kravi26@yahoo.com \
--cc=kernelnewbies@nl.linux.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