From: Timur Tabi <ttabi@interactivesi.com>
To: Linux Kernel Mailing list <linux-kernel@vger.kernel.org>,
Linux MM mailing list <linux-mm@kvack.org>
Subject: Re: iounmap() - can't always unmap memory I've mappedt
Date: Fri, 29 Sep 2000 17:12:58 -0500 [thread overview]
Message-ID: <20000929221248Z131165-244+31@kanga.kvack.org> (raw)
In-Reply-To: <E13f8CX-0001g1-00@the-village.bc.nu>
** Reply to message from Alan Cox <alan@lxorguk.ukuu.org.uk> on Fri, 29 Sep
2000 23:00:16 +0100 (BST)
> > "num_pages" is usually just equal to 1. This code appears to work very well.
> > However, when I call the iounmap function on the memory obtained via
> > ioremap_nocache, sometimes I hit a kernel BUG(). The code which causes the bug
> > is in page_alloc.c, line 85 (in function __free_pages_ok):
> >
> > if (page->buffers)
> > BUG();
>
> This sounds like you are trying to do maps on pages that are in use. No can do
Why not? I mean, I can access the memory anyway from the driver, since it's
all mapped linearly via phys_to_virt. All I'm really doing is creating a
temporary alias.
Unfortunately, this mapping is a requirement for our product. I'd hate to have
to create my own pte's and do it all manually.
What confuses me is what ioremap_nocache() doesn't fail. Why are these tests
(e.g. page->buffers) not in ioremap_nocache()?
--
Timur Tabi - ttabi@interactivesi.com
Interactive Silicon - http://www.interactivesi.com
When replying to a mailing-list message, please don't cc: me, because then I'll just get two copies of the same message.
--
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.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-09-29 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000929221109Z129234-481+1111@vger.kernel.org>
2000-09-29 22:00 ` Alan Cox
2000-09-29 22:12 ` Timur Tabi [this message]
[not found] <20000929222813Z129135-481+1113@vger.kernel.org>
2000-09-29 23:24 ` Alan Cox
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=20000929221248Z131165-244+31@kanga.kvack.org \
--to=ttabi@interactivesi.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