1. 08 5月, 2008 14 次提交
  2. 07 5月, 2008 4 次提交
    • D
      sparc: Fix mmap VA span checking. · 58163393
      David S. Miller 提交于
      We should not conditionalize VA range checks on MAP_FIXED.
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      58163393
    • L
      Revert "uml: fix gcc problem" · c0a18111
      Linus Torvalds 提交于
      This reverts commit 22eecde2.  Uli
      reports that it breaks UML on x86-64 with the Fedora 8 gcc (gcc 4.1.2),
      causing a crash on startup. See
      
      	http://marc.info/?l=linux-kernel&m=121011722806093&w=2
      
      for a trace.
      Reported-by: NUlrich Drepper <drepper@redhat.com>
      Cc: Ingo Molnar <mingo@elte.hu>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      c0a18111
    • D
      sparc64: Fix initrd regression. · d45100f7
      David S. Miller 提交于
      We die because we forget to convert initrd_start and
      initrd_end to virtual addresses.
      
      Reported by Mikael Pettersson
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d45100f7
    • H
      x86: fix PAE pmd_bad bootup warning · aeed5fce
      Hugh Dickins 提交于
      Fix warning from pmd_bad() at bootup on a HIGHMEM64G HIGHPTE x86_32.
      
      That came from 9fc34113 x86: debug pmd_bad();
      but we understand now that the typecasting was wrong for PAE in the previous
      version: pagetable pages above 4GB looked bad and stopped Arjan from booting.
      
      And revert that cded932b x86: fix pmd_bad
      and pud_bad to support huge pages.  It was the wrong way round: we shouldn't
      weaken every pmd_bad and pud_bad check to let huge pages slip through - in
      part they check that we _don't_ have a huge page where it's not expected.
      
      Put the x86 pmd_bad() and pud_bad() definitions back to what they have long
      been: they can be improved (x86_32 should use PTE_MASK, to stop PAE thinking
      junk in the upper word is good; and x86_64 should follow x86_32's stricter
      comparison, to stop thinking any subset of required bits is good); but that
      should be a later patch.
      
      Fix Hans' good observation that follow_page() will never find pmd_huge()
      because that would have already failed the pmd_bad test: test pmd_huge in
      between the pmd_none and pmd_bad tests.  Tighten x86's pmd_huge() check?
      No, once it's a hugepage entry, it can get quite far from a good pmd: for
      example, PROT_NONE leaves it with only ACCESSED of the KERN_PGTABLE bits.
      
      However... though follow_page() contains this and another test for huge
      pages, so it's nice to keep it working on them, where does it actually get
      called on a huge page?  get_user_pages() checks is_vm_hugetlb_page(vma) to
      to call alternative hugetlb processing, as does unmap_vmas() and others.
      Signed-off-by: NHugh Dickins <hugh@veritas.com>
      Earlier-version-tested-by: NIngo Molnar <mingo@elte.hu>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Jeff Chua <jeff.chua.linux@gmail.com>
      Cc: Hans Rosenfeld <hans.rosenfeld@amd.com>
      Cc: Arjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      aeed5fce
  3. 06 5月, 2008 7 次提交
  4. 05 5月, 2008 14 次提交
  5. 04 5月, 2008 1 次提交