Skip to content
Commits on Mar 16, 2013
  1. Merge branch 'distro-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 16, 2013
  2. distro-3.8: disable ASHMEM in Ubuntu

    Oleksandr Natalenko committed Mar 16, 2013
  3. Merge branch 'distro-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 16, 2013
  4. distro-3.8: do not append local version for Arch

    Oleksandr Natalenko committed Mar 16, 2013
  5. Merge branch 'distro-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 16, 2013
  6. distro-3.8: compile EnhanceIO as modules

    Oleksandr Natalenko committed Mar 16, 2013
  7. Merge branch 'distro-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 16, 2013
  8. distro-3.8: update distro config, stage 2/2

    Oleksandr Natalenko committed Mar 16, 2013
  9. Merge branch 'distro-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 16, 2013
  10. distro-3.8: update distro config, stage 1/2

    Oleksandr Natalenko committed Mar 16, 2013
  11. Merge branch 'uksm-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 16, 2013
  12. uksm-3.8: try to fix UKSM boot issue on my laptop

    Oleksandr Natalenko committed Mar 16, 2013
Commits on Mar 15, 2013
  1. Merge branch 'configs-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 15, 2013
  2. configs-3.8: update dell-vostro-3360.config

    Oleksandr Natalenko committed Mar 15, 2013
  3. Merge branch 'ck-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 15, 2013
  4. ck-3.8: remove extra version info

    Oleksandr Natalenko committed Mar 15, 2013
  5. Merge branch 'uksm-3.8' into pf-3.8

    Oleksandr Natalenko committed Mar 15, 2013
  6. uksm-3.8: merge UKSM for Linux v3.8.2

    Oleksandr Natalenko committed Mar 15, 2013
Commits on Mar 14, 2013
  1. fix merge conflict

    Oleksandr Natalenko committed Mar 14, 2013
  2. @gregkh

    Linux 3.8.3

    gregkh committed Mar 14, 2013
  3. @davem330 @gregkh

    6lowpan: Remove __init tag from lowpan_netlink_fini().

    commit a07fdce upstream.
    
    It's called from both __init and __exit code, so neither
    tag is appropriate.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    davem330 committed with gregkh Feb 6, 2013
  4. @ebiederm @gregkh

    userns: Don't allow CLONE_NEWUSER | CLONE_FS

    commit e66eded upstream.
    
    Don't allowing sharing the root directory with processes in a
    different user namespace.  There doesn't seem to be any point, and to
    allow it would require the overhead of putting a user namespace
    reference in fs_struct (for permission checks) and incrementing that
    reference count on practically every call to fork.
    
    So just perform the inexpensive test of forbidding sharing fs_struct
    acrosss processes in different user namespaces.  We already disallow
    other forms of threading when unsharing a user namespace so this
    should be no real burden in practice.
    
    This updates setns, clone, and unshare to disallow multiple user
    namespaces sharing an fs_struct.
    
    Signed-off-by: "Eric W. Biederman" <ebiederm@xmission.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    ebiederm committed with gregkh Mar 13, 2013
  5. @hauke @gregkh

    w1-gpio: fix section mismatch

    commit 06a8f1f upstream.
    
    This fixes the following section mismatch:
    
    WARNING: drivers/w1/masters/w1-gpio.o(.data+0x188): Section mismatch in
    reference from the variable w1_gpio_driver to the function
    .init.text:w1_gpio_probe()
    The variable w1_gpio_driver references
    the function __init w1_gpio_probe()
    If the reference is valid then annotate the
    variable with __init* or __refdata (see linux/init.h) or name the variable:
    *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console
    
    Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
    Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    hauke committed with gregkh Jan 27, 2013
  6. @gregkh

    Revert "xen/blkback: Don't trust the handle from the frontend."

    This reverts commit 01c681d upstream
    (ef56ca6 in this tree), as it wasn't
    supposed to have been applied to the stable tree.
    
    Cc: Jan Beulich <jbeulich@suse.com>
    Cc: Ian Campbell <ian.campbell@citrix.com>
    Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    gregkh committed Mar 12, 2013
  7. @gregkh

    USB: Fix connected device switch to Inactive state.

    [This is upstream commit d3b9d7a.
    It needs to be backported to kernels as old as 3.2, because it fixes the
    buggy commit 65bdac5 "USB: Handle warm
    reset failure on empty port."]
    
    A USB 3.0 device can transition to the Inactive state if a U1 or U2 exit
    transition fails.  The current code in hub_events simply issues a warm
    reset, but does not call any pre-reset or post-reset driver methods (or
    unbind/rebind drivers without them).  Therefore the drivers won't know
    their device has just been reset.
    
    hub_events should instead call usb_reset_device.  This means
    hub_port_reset now needs to figure out whether it should issue a warm
    reset or a hot reset.
    
    Remove the FIXME note about needing disconnect() for a NOTATTACHED
    device.  This patch fixes that.
    
    Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
    Acked-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Sarah Sharp committed with gregkh Mar 7, 2013
  8. @gregkh

    USB: Rip out recursive call on warm port reset.

    [This is upstream commit a24a607.
    It needs to be backported to kernels as old as 3.2, because it fixes the
    buggy commit 65bdac5 "USB: Handle warm
    reset failure on empty port."]
    
    When a hot reset fails on a USB 3.0 port, the current port reset code
    recursively calls hub_port_reset inside hub_port_wait_reset.  This isn't
    ideal, since we should avoid recursive calls in the kernel, and it also
    doesn't allow us to issue multiple warm resets on reset failures.
    
    Rip out the recursive call.  Instead, add code to hub_port_reset to
    issue a warm reset if the hot reset fails, and try multiple warm resets
    before giving up on the port.
    
    In hub_port_wait_reset, remove the recursive call and re-indent.  The
    code is basically the same, except:
    
    1. It bails out early if the port has transitioned to Inactive or
    Compliance Mode after the reset completed.
    
    2. It doesn't consider a connect status change to be a failed reset.  If
    multiple warm resets needed to be issued, the connect status may have
    changed, so we need to ignore that and look at the port link state
    instead.  hub_port_reset will now do that.
    
    3. It unconditionally sets udev->speed on all types of successful
    resets.  The old recursive code would set the port speed when the second
    hub_port_reset returned.
    
    The old code did not handle connected devices needing a warm reset well.
    There were only two situations that the old code handled correctly: an
    empty port needing a warm reset, and a hot reset that migrated to a warm
    reset.
    
    When an empty port needed a warm reset, hub_port_reset was called with
    the warm variable set.  The code in hub_port_finish_reset would skip
    telling the USB core and the xHC host that the device was reset, because
    otherwise that would result in a NULL pointer dereference.
    
    When a USB 3.0 device reset migrated to a warm reset, the recursive call
    made the call stack look like this:
    
    hub_port_reset(warm = false)
            hub_wait_port_reset(warm = false)
                    hub_port_reset(warm = true)
                            hub_wait_port_reset(warm = true)
                            hub_port_finish_reset(warm = true)
                            (return up the call stack to the first wait)
    
            hub_port_finish_reset(warm = false)
    
    The old code didn't want to notify the USB core or the xHC host of device reset
    twice, so it only did it in the second call to hub_port_finish_reset,
    when warm was set to false.  This was necessary because
    before patch two ("USB: Ignore xHCI Reset Device status."), the USB core
    would pay attention to the xHC Reset Device command error status, and
    the second call would always fail.
    
    Now that we no longer have the recursive call, and warm can change from
    false to true in hub_port_reset, we need to have hub_port_finish_reset
    unconditionally notify the USB core and the xHC of the device reset.
    
    In hub_port_finish_reset, unconditionally clear the connect status
    change (CSC) bit for USB 3.0 hubs when the port reset is done.  If we
    had to issue multiple warm resets for a device, that bit may have been
    set if the device went into SS.Inactive and then was successfully warm
    reset.
    
    Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
    Acked-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Sarah Sharp committed with gregkh Mar 7, 2013
  9. @gregkh

    USB: Prepare for refactoring by adding extra udev checks.

    [This is upstream commit 2d4fa94.
    It needs to be backported to kernels as old as 3.2, because it fixes the
    buggy commit 65bdac5 "USB: Handle warm
    reset failure on empty port."]
    
    The next patch will refactor the hub port code to rip out the recursive
    call to hub_port_reset on a failed hot reset.  In preparation for that,
    make sure all code paths can deal with being called with a NULL udev.
    The usb_device will not be valid if warm reset was issued because a port
    transitioned to the Inactive or Compliance Mode on a device connect.
    
    This patch should have no effect on current behavior.
    
    Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
    Acked-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Sarah Sharp committed with gregkh Mar 7, 2013
  10. @gregkh

    USB: Don't use EHCI port sempahore for USB 3.0 hubs.

    [This is upstream commit 0fe51aa.
    It needs to be backported to kernels as old as 3.2, because it fixes the
    buggy commit 65bdac5 "USB: Handle warm
    reset failure on empty port."]
    
    The EHCI host controller needs to prevent EHCI initialization when the
    UHCI or OHCI companion controller is in the middle of a port reset.  It
    uses ehci_cf_port_reset_rwsem to do this.  USB 3.0 hubs can't be under
    an EHCI host controller, so it makes no sense to down the semaphore for
    USB 3.0 hubs.  It also makes the warm port reset code more complex.
    
    Don't down ehci_cf_port_reset_rwsem for USB 3.0 hubs.
    
    Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
    Acked-by: Alan Stern <stern@rowland.harvard.edu>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Sarah Sharp committed with gregkh Mar 7, 2013
  11. @gregkh

    efi: be more paranoid about available space when creating variables

    commit 68d9298 upstream.
    
    UEFI variables are typically stored in flash. For various reasons, avaiable
    space is typically not reclaimed immediately upon the deletion of a
    variable - instead, the system will garbage collect during initialisation
    after a reboot.
    
    Some systems appear to handle this garbage collection extremely poorly,
    failing if more than 50% of the system flash is in use. This can result in
    the machine refusing to boot. The safest thing to do for the moment is to
    forbid writes if they'd end up using more than half of the storage space.
    We can make this more finegrained later if we come up with a method for
    identifying the broken machines.
    
    Signed-off-by: Matthew Garrett <matthew.garrett@nebula.com>
    Cc: Josh Boyer <jwboyer@redhat.com>
    Signed-off-by: Matt Fleming <matt.fleming@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Matthew Garrett committed with gregkh Mar 2, 2013
  12. @gregkh

    efivars: Disable external interrupt while holding efivars->lock

    commit 81fa4e5 upstream.
    
    [Problem]
    There is a scenario which efi_pstore fails to log messages in a panic case.
    
     - CPUA holds an efi_var->lock in either efivarfs parts
       or efi_pstore with interrupt enabled.
     - CPUB panics and sends IPI to CPUA in smp_send_stop().
     - CPUA stops with holding the lock.
     - CPUB kicks efi_pstore_write() via kmsg_dump(KSMG_DUMP_PANIC)
       but it returns without logging messages.
    
    [Patch Description]
    This patch disables an external interruption while holding efivars->lock
    as follows.
    
    In efi_pstore_write() and get_var_data(), spin_lock/spin_unlock is
    replaced by spin_lock_irqsave/spin_unlock_irqrestore because they may
    be called in an interrupt context.
    
    In other functions, they are replaced by spin_lock_irq/spin_unlock_irq.
    because they are all called from a process context.
    
    By applying this patch, we can avoid the problem above with
    a following senario.
    
     - CPUA holds an efi_var->lock with interrupt disabled.
     - CPUB panics and sends IPI to CPUA in smp_send_stop().
     - CPUA receives the IPI after releasing the lock because it is
       disabling interrupt while holding the lock.
     - CPUB waits for one sec until CPUA releases the lock.
     - CPUB kicks efi_pstore_write() via kmsg_dump(KSMG_DUMP_PANIC)
       And it can hold the lock successfully.
    
    Signed-off-by: Seiji Aguchi <seiji.aguchi@hds.com>
    Acked-by: Mike Waychison <mikew@google.com>
    Acked-by: Matt Fleming <matt.fleming@intel.com>
    Signed-off-by: Tony Luck <tony.luck@intel.com>
    Cc: Josh Boyer <jwboyer@redhat.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Seiji Aguchi committed with gregkh Feb 12, 2013
  13. @gregkh

    ftrace: Update the kconfig for DYNAMIC_FTRACE

    commit db05021 upstream.
    
    The prompt to enable DYNAMIC_FTRACE (the ability to nop and
    enable function tracing at run time) had a confusing statement:
    
     "enable/disable ftrace tracepoints dynamically"
    
    This was written before tracepoints were added to the kernel,
    but now that tracepoints have been added, this is very confusing
    and has confused people enough to give wrong information during
    presentations.
    
    Not only that, I looked at the help text, and it still references
    that dreaded daemon that use to wake up once a second to update
    the nop locations and brick NICs, that hasn't been around for over
    five years.
    
    Time to bring the text up to the current decade.
    
    Reported-by: Ezequiel Garcia <elezegarcia@gmail.com>
    Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Steven Rostedt committed with gregkh Feb 27, 2013
  14. @mpe @gregkh

    powerpc: Apply early paca fixups to boot_paca and the boot cpu's paca

    commit 25e1381 upstream.
    
    In commit 466921c we added a hack to set the paca data_offset to zero so
    that per-cpu accesses would work on the boot cpu prior to per-cpu areas
    being setup. This fixed a problem with lockdep touching per-cpu areas
    very early in boot.
    
    However if we combine CONFIG_LOCK_STAT=y with any of the PPC_EARLY_DEBUG
    options, we can hit the same problem in udbg_early_init(). To avoid that
    we need to set the data_offset of the boot_paca also. So factor out the
    fixup logic and call it for both the boot_paca, and "the paca of the
    boot cpu".
    
    Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
    Tested-by: Geoff Levand <geoff@infradead.org>
    Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    mpe committed with gregkh Feb 12, 2013
  15. @gregkh

    ARM: kirkwood: of_serial: fix clock gating by removing clock-frequency

    commit 93fff4c upstream.
    
    When DT support for kirkwood was first introduced, there was no clock
    infrastructure.  As a result, we had to manually pass the
    clock-frequency to the driver from the device node.
    
    Unfortunately, on kirkwood, with minimal config or all module configs,
    clock-frequency breaks booting because of_serial doesn't consume the
    gate_clk when clock-frequency is defined.
    
    The end result on kirkwood is that runit gets gated, and then the boot
    fails when the kernel tries to write to the serial port.
    
    Fix the issue by removing the clock-frequency parameter from all
    kirkwood dts files.
    
    Booted on dreamplug without earlyprintk and successfully logged in via
    ttyS0.
    
    Reported-by: Simon Baatz <gmbnomis@gmail.com>
    Tested-by: Simon Baatz <gmbnomis@gmail.com>
    Signed-off-by: Jason Cooper <jason@lakedaemon.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Jason Cooper committed with gregkh Jan 29, 2013
  16. @gregkh

    ARM: mxs_defconfig: Make USB host functional again

    commit f6c49da upstream.
    
    commit 09f6ffd (USB: EHCI: fix build error by making ChipIdea host a normal
    EHCI driver) introduced CONFIG_USB_EHCI_HCD as a dependency for USB_CHIPIDEA_HOST.
    
    Select CONFIG_USB_EHCI_HCD, so that USB host can be functional again.
    
    Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
    Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    Fabio Estevam committed with gregkh Feb 27, 2013
  17. @lunn @gregkh

    gpio: mvebu: Add clk support to prevent lockup

    commit de88747 upstream.
    
    The kirkwood SoC GPIO cores use the runit clock. Add code to
    clk_prepare_enable() runit, otherwise there is a danger of locking up
    the SoC by accessing the GPIO registers when runit clock is not
    ticking.
    
    Reported-by: Simon Baatz <gmbnomis@gmail.com>
    Signed-off-by: Andrew Lunn <andrew@lunn.ch>
    Tested-by: Simon Baatz <gmbnomis@gmail.com>
    Acked-by: Linus Walleij <linus.walleij@linaro.org>
    Signed-off-by: Jason Cooper <jason@lakedaemon.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
    lunn committed with gregkh Feb 3, 2013
Something went wrong with that request. Please try again.