From: Hugh Dickins <hugh@veritas.com>
To: Nadia Derbey <Nadia.Derbey@bull.net>
Cc: Franck Bui-Huu <fbuihuu@gmail.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: unable to mmap /dev/kmem
Date: Thu, 18 Jan 2007 18:04:41 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0701181743340.25435@blonde.wat.veritas.com> (raw)
In-Reply-To: <45AFA490.5000508@bull.net>
On Thu, 18 Jan 2007, Nadia Derbey wrote:
>
> Trying to mmap /dev/kmem with an offset I take from /boot/System.map,
> I get an EIO error on a 2.6.20-rc4.
> This is something that used to work on older kernels.
>
> Had a look at mmap_kmem() in drivers/char/mem.c, and I'm wondering whether
> pfn is correctly computed there: shouldn't we have something like
>
> pfn = PFN_DOWN(virt_to_phys((void *)PAGE_OFFSET)) +
> __pa(vma->vm_pgoff << PAGE_SHIFT);
>
> instead of
>
> pfn = PFN_DOWN(virt_to_phys((void *)PAGE_OFFSET)) + vma->vm_pgoff;
>
> Or may be should I substract PAGE_OFFSET from the value I get from System.map
> before mmapping /dev/kmem?
Sigh, you're right, 2.6.19 messed that up completely.
No, you never had to subtract PAGE_OFFSET from that address
in the past, and you shouldn't have to do so now.
Please revert the offending patch below, and then maybe Franck
can come up with a patch which preserves the original behaviour
on architectures which used to work (e.g. i386), while fixing
it for those architectures (which are they?) that did not.
I guess it's reassuring to know that not many are actually
using mmap of /dev/kmem, so you're the first to notice: thanks.
Hugh
From: Franck Bui-Huu <fbuihuu@gmail.com>
Date: Thu, 12 Oct 2006 19:06:33 +0000 (+0200)
Subject: [PATCH] Fix up mmap_kmem
X-Git-Tag: v2.6.19-rc2^0~6
X-Git-Url: http://127.0.0.1:1234/?p=.git;a=commitdiff_plain;h=99a10a60ba9bedcf5d70ef81414d3e03816afa3f;hp=a5344a9555fffd045218aced89afd6ca0f884e10
[PATCH] Fix up mmap_kmem
vma->vm_pgoff is an pfn _offset_ relatif to the begining
of the memory start. The previous code was doing at first:
vma->vm_pgoff << PAGE_SHIFT
which results into a wrong physical address since some
platforms have a physical mem start that can be different
from 0. After that the previous call __pa() on this
wrong physical address, however __pa() is used to convert
a _virtual_ address into a physical one.
This patch rewrites this convertion. It calculates the
pfn of PAGE_OFFSET which is the pfn of the mem start
then it adds the vma->vm_pgoff to it.
It also uses virt_to_phys() instead of __pa() since the
latter shouldn't be used by drivers.
Signed-off-by: Franck Bui-Huu <fbuihuu@gmail.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
---
diff --git a/drivers/char/mem.c b/drivers/char/mem.c
index 6511012..a89cb52 100644
--- a/drivers/char/mem.c
+++ b/drivers/char/mem.c
@@ -292,8 +292,8 @@ static int mmap_kmem(struct file * file,
{
unsigned long pfn;
- /* Turn a kernel-virtual address into a physical page frame */
- pfn = __pa((u64)vma->vm_pgoff << PAGE_SHIFT) >> PAGE_SHIFT;
+ /* Turn a pfn offset into an absolute pfn */
+ pfn = PFN_DOWN(virt_to_phys((void *)PAGE_OFFSET)) + vma->vm_pgoff;
/*
* RED-PEN: on some architectures there is more mapped memory
next prev parent reply other threads:[~2007-01-18 18:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 16:47 Nadia Derbey
2007-01-18 18:04 ` Hugh Dickins [this message]
2007-01-19 6:26 ` Nadia Derbey
2007-01-19 9:10 ` Nadia Derbey
2007-01-19 16:33 ` Hugh Dickins
2007-01-19 16:57 ` Arjan van de Ven
2007-01-19 17:12 ` Hugh Dickins
2007-01-19 17:27 ` Arjan van de Ven
2007-01-19 17:52 ` Hugh Dickins
2007-01-19 21:57 ` Andi Kleen
2007-01-19 11:31 ` Franck Bui-Huu
2007-01-19 17:02 ` Hugh Dickins
2007-01-20 17:19 ` Franck Bui-Huu
2007-01-21 9:56 ` Hugh Dickins
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.64.0701181743340.25435@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=Nadia.Derbey@bull.net \
--cc=fbuihuu@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®