linux-kernel - Re: 2.6.25-gitX and pmd_bad() on x86

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

Date:	Fri, 25 Apr 2008 11:48:02 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Joerg Friedrich <Joerg.Friedrich@...edrich-kn.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.25-gitX and pmd_bad() on x86_32

Joerg Friedrich <Joerg.Friedrich@...edrich-kn.de> writes:

> Yesterday I tried to compile 2.6.25-git5 but I ran into a "Unknown
> Symbol" (pmd_bad)  warning from linker while compiling the nvidia-binary module.

pmd_bad is always optional. You can safely make it return 0 in some local
macro.

> AFAICS, x86_32 is the only architecture where pmd_bad is neither a
> define or a static inline. Including asm/pgtable.h is no longer
> sufficient on x868_32. Is this behaviour intended or is there just a
> EXPORT_SYMBOL missing?

Kernel changes generally don't care about out of tree modules.
Also pmd_bad() is kind of internal anyways.

-Andi
--
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/