linux-kernel - [PATCH 0/3] Globally defining phys_addr

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

Message-ID: <48C8D76B.10901@goop.org>
Date:	Thu, 11 Sep 2008 01:31:39 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Alex Nixon <alex.nixon@...rix.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/3] Globally defining phys_addr_t

Hi Ingo,

This is a repost of a little 3-patch series which Andrew has been
carrying in -mm.  It cleans up the definition of phys_addr_t to make it
kernel-wide rather than x86-specific, and fixes up PFN_PHYS() to use it
to avoid address truncation.

We currently have a few workarounds for this problem in the tree, but
Alex found another bug caused by PFN_PHYS(), so it's probably better if
you bring these patches into tip.git for now.

PowerPC also defines a phys_addr_t with the same meaning as x86; the
powerpc arch maintainers are happy with these patches.

The third patch in the series is not necessary to fix any bug, but it
removes the separate definition of resource_size_t to define it in terms
of phys_addr_t.  I include it for competeness.

Thanks,
    J
--
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/