linux-kernel - Re: exported version of page_is

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 5 May 2008 17:13:46 -0400
From:	"Timur Alperovich" <timur.alperovich@...il.com>
To:	"Arjan van de Ven" <arjan@...radead.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: exported version of page_is_ram?

I put the whole driver on pastebin http://pastebin.com/m24c50118
For now I tried to use the code for page_is_ram in there, only to
realize that e820 struct is also not exported. Is there a way to do
this with the existing code in the kernel, since I'd like the code to
run on older 2.6 kernels as well?

Timur

On Mon, May 5, 2008 at 3:50 PM, Arjan van de Ven <arjan@...radead.org> wrote:
>
> On Mon, 5 May 2008 13:58:59 -0400
>  "Timur Alperovich" <timur.alperovich@...il.com> wrote:
>
>  > Hi,
>  >
>  > I need to check if a given page is in ram or not. It seems that
>  > page_is_ram does the trick, but since it's not exported, I end up with
>  > "unknown symbol" errors when I try to insert the module. I'm trying to
>  > hash the contents of every page in physical memory, and iterating
>  > through pages from 0 to num_physpages, while checking if they are
>  > actually in ram seemed reasonable. Is there a better way to do it or
>  > is there another function rather than page_is_ram that can do the
>  > trick?
>
>  sounds like the right way is to make a "for each ram page" function
>  in the core, export_symbol_gpl that so that you can then use that...
>  We could even make it scale and numa friendly in the core that way.
>
>  Do you have a url for your code?
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/