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:	Thu, 07 Jun 2007 21:29:28 +1000
From:	Nick Piggin <nickpiggin@...oo.com.au>
To:	"Robert P. J. Day" <rpjday@...dspring.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: why does the macro "ZERO_PAGE" take an argument?

Robert P. J. Day wrote:
>   probably making a fool of myself here, but what is the purpose of
> that single argument to the macro "ZERO_PAGE"?
> 
> $ grep -r "define ZERO_PAGE" include
> include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr)      ({ BUG(); NULL; })
> include/asm-frv/pgtable.h:#define ZERO_PAGE(vaddr)      virt_to_page(empty_zero_page)
> include/asm-v850/pgtable.h:#define ZERO_PAGE(vaddr)     ((void *)0x87654321)
> include/asm-mips/pgtable.h:#define ZERO_PAGE(vaddr) \
> include/asm-blackfin/pgtable.h:#define ZERO_PAGE(vaddr) (virt_to_page(0))
> include/asm-parisc/pgtable.h:#define ZERO_PAGE(vaddr) (virt_to_page(empty_zero_page))
> include/asm-alpha/pgtable.h:#define ZERO_PAGE(vaddr)    (virt_to_page(ZERO_PGE))
> ...
> 
>   AFAICT, there are no definitions of that macro that actually use
> that argument.  is that some kind of historical cruft?

MIPS?

-- 
SUSE Labs, Novell Inc.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ