linux-kernel - [GIT PULL] x86: clean up use of system_state in virt_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]

Date:	Wed, 04 Mar 2009 18:15:12 -0800
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	the arch/x86 maintainers <x86@...nel.org>,
	Jiri Slaby <jirislaby@...il.com>,
	Vegard Nossum <vegard.nossum@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: [GIT PULL] x86: clean up use of system_state in virt_addr_valid and
 co

These two changes remove the tests based on system_state in the virt_addr_valid/phys_addr functions.
It replaces the i386 test with an explicit flag to indicate whether the vmalloc range has been determined,
and on x86-64, it pre-initializes the x86_phys_bits to a reasonable number so that there's no dependency
on init order.

	J

The following changes since commit 4d02f9f7dac27f801fed69be8ebb0b95b798b12c:
  Ingo Molnar (1):
        Merge branch 'x86/urgent'

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git x86/virt

Jeremy Fitzhardinge (2):
      x86-32: use specific __vmalloc_start_set flag in __virt_addr_valid
      x86-64: pre-initialize boot_cpu_data.x86_phys_bits to avoid system_state tests

 arch/x86/include/asm/pgtable_32_types.h |    5 +++++
 arch/x86/kernel/setup.c                 |    4 +++-
 arch/x86/mm/init_32.c                   |    3 +++
 arch/x86/mm/ioremap.c                   |   14 +++++---------
 4 files changed, 16 insertions(+), 10 deletions(-)


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