linux-kernel - Wrong __pa() usages in driver/char/mem.c ?

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>] [day] [month] [year] [list]

Message-ID: <452E3451.1090907@innova-card.com>
Date:	Thu, 12 Oct 2006 14:25:53 +0200
From:	Franck Bui-Huu <vagabon.xyz@...il.com>
To:	Andrew Morton <akpm@...l.org>
CC:	Atsushi Nemoto <anemo@....ocn.ne.jp>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Wrong __pa() usages in driver/char/mem.c ?

I'm suprised to find some __pa() usages in a driver. I would
have used virt_to_phys() instead. In my understanding __pa()
is used only during early bootmem init, because this macro
is aware of any weird things that might exist at this early 
stage. But once this stage is completed virt_to_phys() should
be used.

Is this understanding wrong ?

Thanks
		Franck
-
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/