15 Jun, 2010

7 commits

  • Irq stacks provide an essential protection from stack overflows through
    external interrupts, at the cost of two additionals stacks per CPU.

    Enable them unconditionally to simplify the kernel build and prevent
    people from accidentally disabling them.

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Benjamin Herrenschmidt

    Christoph Hellwig
     
  • kexec_perpare_cpus_wait() iterates i through NR_CPUS to check
    paca[i].kexec_state of each to make sure they have quiesced.
    However now we have dynamic PACA allocation, paca[NR_CPUS] is not necessarily
    valid and we overrun the array; spurious "cpu is not possible, ignoring"
    errors result. This patch iterates for_each_online_cpu so stays
    within the bounds of paca[] -- and every CPU is now 'possible'.

    Signed-off-by: Matt Evans
    Signed-off-by: Benjamin Herrenschmidt

    Matt Evans
     
  • Acked-by: Grant Likely

    On 5 May 2010 21:33, "Anton Blanchard" wrote:

    CONFIG_SYSFS_DEPRECATED can cause issues with newer distros and should not
    be required for any distro in the last 3 or 4 years, so disable it.

    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Grant Likely
     
  • It was used in the dim distant past for adding initrds to images
    for legacy iSeries, but it's not even used for that now that we
    have initramfs. So remove it.

    Signed-off-by: Paul Mackerras
    Signed-off-by: Benjamin Herrenschmidt

    Paul Mackerras
     
  • We are seeing boot fails on some System p machines when using the kdump
    crashkernel= boot option. The default kdump base address is 32MB, so if we
    reserve 256MB for kdump then we reserve all of the RMO except the first 32MB.

    We really want kdump to reserve some memory in the RMO and most of it
    elsewhere but that will require more significant changes. For now we can shift
    the default base address to 64MB when CONFIG_PPC64 and CONFIG_RELOCATABLE are
    set. This isn't quite correct since what we really care about is the kdump
    kernel is relocatable, but we already make the assumption that base kernel
    and kdump kernel have the same CONFIG_RELOCATABLE setting, eg:

    #ifndef CONFIG_RELOCATABLE
    if (crashk_res.start != KDUMP_KERNELBASE)
    printk("Crash kernel location must be 0x%x\n",
    KDUMP_KERNELBASE);
    ...

    RTAS is instantiated towards the top of our RMO, so if we were to go any
    higher we risk not having enough RMO memory for the kdump kernel on boxes
    with a 128MB RMO.

    Signed-off-by: Anton Blanchard
    Signed-off-by: Benjamin Herrenschmidt

    Anton Blanchard
     
  • CONFIG_HIGHPTE doesn't exist in Kconfig, therefore removing all
    references for it from the source code.

    Signed-off-by: Christoph Egger
    Signed-off-by: Benjamin Herrenschmidt

    Christoph Egger
     
  • Benjamin Herrenschmidt
     

12 Jun, 2010

27 commits


11 Jun, 2010

6 commits

  • when we use remap_file_pages() to remap a file, remap_file_pages always return
    error. It is because btrfs didn't set VM_CAN_NONLINEAR for vma.

    Signed-off-by: Miao Xie
    Signed-off-by: Chris Mason

    Miao Xie
     
  • refs can be used with uninitialized data if btrfs_lookup_extent_info()
    fails on the first pass through the loop. In the original code if that
    happens then check_path_shared() probably returns 1, this patch
    changes it to return 1 for safety.

    Signed-off-by: Dan Carpenter
    Signed-off-by: Chris Mason

    Dan Carpenter
     
  • Seems that when btrfs_fallocate was converted to use the new ENOSPC stuff we
    dropped passing the mode to the function that actually does the preallocation.
    This breaks anybody who wants to use FALLOC_FL_KEEP_SIZE. Thanks,

    Signed-off-by: Josef Bacik
    Signed-off-by: Chris Mason

    Josef Bacik
     
  • We cannot use the loop device which has been connected to a file in the btrf

    The reproduce steps is following:
    # dd if=/dev/zero of=vdev0 bs=1M count=1024
    # losetup /dev/loop0 vdev0
    # mkfs.btrfs /dev/loop0
    ...
    failed to zero device start -5

    The reason is that the btrfs don't implement either ->write_begin or ->write
    the VFS API, so we fix it by setting ->write to do_sync_write().

    Signed-off-by: Miao Xie
    Signed-off-by: Chris Mason

    Miao Xie
     
  • fix a race at the end of NAPI complete processing, it had
    better do __napi_complete() first before re-enable interrupt.

    Signed-off-by:Figo.zhang

    Signed-off-by: David S. Miller

    Figo.zhang
     
  • This patch correct a bug in the delay of pktgen.
    It makes sure the inter-packet interval is accurate.

    Signed-off-by: Daniel Turull
    Signed-off-by: Robert Olsson
    Signed-off-by: David S. Miller

    Daniel Turull