Skip to content
Commits on Dec 17, 2012
  1. @gregkh

    Linux 3.4.24

    gregkh committed
  2. @gregkh

    rcu: Fix batch-limit size problem

    Eric Dumazet committed with gregkh
    commit 878d743 upstream.
    Commit 29c00b4 (rcu: Add event-tracing for RCU callback
    invocation) added a regression in rcu_do_batch()
    Under stress, RCU is supposed to allow to process all items in queue,
    instead of a batch of 10 items (blimit), but an integer overflow makes
    the effective limit being 1.  So, unless there is frequent idle periods
    (during which RCU ignores batch limits), RCU can be forced into a
    state where it cannot keep up with the callback-generation rate,
    eventually resulting in OOM.
    This commit therefore converts a few variables in rcu_do_batch() from
    int to long to fix this problem, along with the module parameters
    controlling the batch limits.
    Signed-off-by: Eric Dumazet <>
    Signed-off-by: Paul E. McKenney <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @gnehzuil @gregkh

    perf test: fix a build error on builtin-test

    gnehzuil committed with gregkh
    commit 12f8f74 upstream.
    Recently I build perf and get a build error on builtin-test.c. The error is as
    $ make
        CC perf.o
        CC builtin-test.o
    cc1: warnings being treated as errors
    builtin-test.c: In function ‘sched__get_first_possible_cpu’:
    builtin-test.c:977: warning: implicit declaration of function ‘CPU_ALLOC’
    builtin-test.c:977: warning: nested extern declaration of ‘CPU_ALLOC’
    builtin-test.c:977: warning: assignment makes pointer from integer without a cast
    builtin-test.c:978: warning: implicit declaration of function ‘CPU_ALLOC_SIZE’
    builtin-test.c:978: warning: nested extern declaration of ‘CPU_ALLOC_SIZE’
    builtin-test.c:979: warning: implicit declaration of function ‘CPU_ZERO_S’
    builtin-test.c:979: warning: nested extern declaration of ‘CPU_ZERO_S’
    builtin-test.c:982: warning: implicit declaration of function ‘CPU_FREE’
    builtin-test.c:982: warning: nested extern declaration of ‘CPU_FREE’
    builtin-test.c:992: warning: implicit declaration of function ‘CPU_ISSET_S’
    builtin-test.c:992: warning: nested extern declaration of ‘CPU_ISSET_S’
    builtin-test.c:998: warning: implicit declaration of function ‘CPU_CLR_S’
    builtin-test.c:998: warning: nested extern declaration of ‘CPU_CLR_S’
    make: *** [builtin-test.o] Error 1
    This problem is introduced in 3e7c439. CPU_ALLOC and related macros are
    missing in sched__get_first_possible_cpu function. In 54489c1, commiter
    mentioned that CPU_ALLOC has been removed. So CPU_ALLOC calls in this
    function are removed to let perf to be built.
    Signed-off-by: Vinson Lee <>
    Signed-off-by: Zheng Liu <>
    Cc: David Ahern <>
    Cc: Frederic Weisbecker <>
    Cc: Mike Galbraith <>
    Cc: Paul Mackerras <>
    Cc: Peter Zijlstra <>
    Cc: Stephane Eranian <>
    Cc: Vinson Lee <>
    Cc: Zheng Liu <>
    Signed-off-by: Arnaldo Carvalho de Melo <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @dcbw @gregkh

    cdc-acm: implement TIOCSSERIAL to avoid blocking close(2)

    dcbw committed with gregkh
    commit ba2d8ce upstream.
    Some devices (ex Nokia C7) simply don't respond at all when data is sent
    to some of their USB interfaces.  The data gets stuck in the TTYs queue
    and sits there until close(2), which them blocks because closing_wait
    defaults to 30 seconds (even though the fd is O_NONBLOCK).  This is
    rarely desired.  Implement the standard mechanism to adjust closing_wait
    and let applications handle it how they want to.
    See also 02303f7 for usb_wwan.c.
    Signed-off-by: Dan Williams <>
    Acked-by: Oliver Neukum <>
    Tested-by: Aleksander Morgado <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @gregkh

    ftrace: Clear bits properly in reset_iter_read()

    Dan Carpenter committed with gregkh
    commit 70f77b3 upstream.
    There is a typo here where '&' is used instead of '|' and it turns the
    statement into a noop.  The original code is equivalent to:
    	iter->flags &= ~((1 << 2) & (1 << 4));
    Signed-off-by: Dan Carpenter <>
    Signed-off-by: Steven Rostedt <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @gregkh

    xhci: Extend Fresco Logic MSI quirk.

    Sarah Sharp committed with gregkh
    commit bba18e3 upstream.
    Ali reports that plugging a device into the Fresco Logic xHCI host with
    PCI device ID 1400 produces an IRQ error:
     do_IRQ: 3.176 No irq handler for vector (irq -1)
    Other early Fresco Logic host revisions don't support MSI, even though
    their PCI config space claims they do.  Extend the quirk to disabling
    MSI to this chipset revision.  Also enable the short transfer quirk,
    since it's likely this revision also has that quirk, and it should be
    harmless to enable.
    04:00.0 0c03: 1b73:1400 (rev 01) (prog-if 30 [XHCI])
            Subsystem: 1d5c:1000
            Physical Slot: 3
            Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
            Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
            Latency: 0, Cache Line Size: 64 bytes
            Interrupt: pin A routed to IRQ 51
            Region 0: Memory at d4600000 (32-bit, non-prefetchable) [size=64K]
            Capabilities: [50] Power Management version 3
                    Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-)
                    Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
            Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
                    Address: 00000000feeff00c  Data: 41b1
            Capabilities: [80] Express (v1) Endpoint, MSI 00
                    DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <2us, L1 <32us
                            ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
                    DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
                            RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                            MaxPayload 128 bytes, MaxReadReq 512 bytes
                    DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
                    LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 unlimited, L1 unlimited
                            ClockPM- Surprise- LLActRep- BwNot-
                    LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk+
                            ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
                    LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
            Kernel driver in use: xhci_hcd
    This patch should be backported to stable kernels as old as 2.6.36, that
    contain the commit f5182b4 "xhci:
    Disable MSI for some Fresco Logic hosts."
    Signed-off-by: Sarah Sharp <>
    Reported-by: A Sh <>
    Tested-by: A Sh <>
    Signed-off-by: Greg Kroah-Hartman <>
  7. @gregkh

    USB: OHCI: workaround for hardware bug: retired TDs not added to the …

    Alan Stern committed with gregkh
    …Done Queue
    commit 50ce5c0 upstream.
    This patch (as1636) is a partial workaround for a hardware bug
    affecting OHCI controllers by NVIDIA at least, maybe others too.  When
    the controller retires a Transfer Descriptor, it is supposed to add
    the TD onto the Done Queue.  But sometimes this doesn't happen, with
    the result that ohci-hcd never realizes the corresponding transfer has
    finished.  Symptoms can vary; a typical result is that USB audio stops
    working after a while.
    The patch works around the problem by recognizing that TDs are always
    processed in order.  Therefore, if a later TD is found on the Done
    Queue than all the earlier TDs for the same endpoint must be finished
    as well.
    Unfortunately this won't solve the problem in cases where the missing
    TD is the last one in the endpoint's queue.  A complete fix would
    require a signficant amount of change to the driver.
    Signed-off-by: Alan Stern <>
    Tested-by: Oliver Neukum <>
    Signed-off-by: Greg Kroah-Hartman <>
  8. @zhang-rui @gregkh

    ACPI / video: ignore BIOS initial backlight value for HP Folio 13-2000

    zhang-rui committed with gregkh
    commit 129ff8f upstream.
    Or else the laptop will boot with a dimmed screen.
    Tested-by: Stefan Nagy <>
    Signed-off-by: Zhang Rui <>
    Signed-off-by: Rafael J. Wysocki <>
    Signed-off-by: Greg Kroah-Hartman <>
  9. @gregkh

    ACPI / PNP: Do not crash due to stale pointer use during system resume

    Rafael J. Wysocki committed with gregkh
    commit a6b5e88 upstream.
    During resume from system suspend the 'data' field of
    struct pnp_dev in pnpacpi_set_resources() may be a stale pointer,
    due to removal of the associated ACPI device node object in the
    previous suspend-resume cycle.  This happens, for example, if a
    dockable machine is booted in the docking station and then suspended
    and resumed and suspended again.  If that happens,
    pnpacpi_build_resource_template() called from pnpacpi_set_resources()
    attempts to use that pointer and crashes.
    However, pnpacpi_set_resources() actually checks the device's ACPI
    handle, attempts to find the ACPI device node object attached to it
    and returns an error code if that fails, so in fact it knows what the
    correct value of dev->data should be.  Use this observation to update
    dev->data with the correct value if necessary and dump a call trace
    if that's the case (once).
    We still need to fix the root cause of this issue, but preventing
    systems from crashing because of it is an improvement too.
    Reported-and-tested-by: Zdenek Kabelac <>
    Signed-off-by: Rafael J. Wysocki <>
    Signed-off-by: Greg Kroah-Hartman <>
  10. @gregkh

    ACPI / PM: Add Sony Vaio VPCEB1S1E to nonvs blacklist.

    Lan Tianyu committed with gregkh
    commit 876ab79 upstream.
    Sony Vaio VPCEB1S1E does not resume correctly without
    acpi_sleep=nonvs, so add it to the ACPI sleep blacklist.
    Reported-by: Sébastien Wilmet <>
    Signed-off-by: Lan Tianyu <>
    Signed-off-by: Rafael J. Wysocki <>
    Signed-off-by: Greg Kroah-Hartman <>
  11. @gregkh

    ACPI / battery: Correct battery capacity values on Thinkpads

    Kamil Iskra committed with gregkh
    commit 4000e62 upstream.
    Add a quirk to correctly report battery capacity on 2010 and 2011
    Lenovo Thinkpad models.
    The affected models that I tested (x201, t410, t410s, and x220)
    exhibit a problem where, when battery capacity reporting unit is mAh,
    the values being reported are wrong.  Pre-2010 and 2012 models appear
    to always report in mWh and are thus unaffected.  Also, in mid-2012
    Lenovo issued a BIOS update for the 2011 models that fixes the issue
    (tested on x220 with a post-1.29 BIOS).  No such update is available
    for the 2010 models, so those still need this patch.
    Problem description: for some reason, the affected Thinkpads switch
    the reporting unit between mAh and mWh; generally, mAh is used when a
    laptop is plugged in and mWh when it's unplugged, although a
    suspend/resume or rmmod/modprobe is needed for the switch to take
    effect.  The values reported in mAh are *always* wrong.  This does
    not appear to be a kernel regression; I believe that the values were
    never reported correctly.  I tested back to kernel 2.6.34, with
    multiple machines and BIOS versions.
    Simply plugging a laptop into mains before turning it on is enough to
    reproduce the problem.  Here's a sample /proc/acpi/battery/BAT0/info
    from Thinkpad x220 (before a BIOS update) with a 4-cell battery:
    present:                 yes
    design capacity:         2886 mAh
    last full capacity:      2909 mAh
    battery technology:      rechargeable
    design voltage:          14800 mV
    design capacity warning: 145 mAh
    design capacity low:     13 mAh
    cycle count:              0
    capacity granularity 1:  1 mAh
    capacity granularity 2:  1 mAh
    model number:            42T4899
    serial number:           21064
    battery type:            LION
    OEM info:                SANYO
    Once the laptop switches the unit to mWh (unplug from mains, suspend,
    resume), the output changes to:
    present:                 yes
    design capacity:         28860 mWh
    last full capacity:      29090 mWh
    battery technology:      rechargeable
    design voltage:          14800 mV
    design capacity warning: 1454 mWh
    design capacity low:     200 mWh
    cycle count:              0
    capacity granularity 1:  1 mWh
    capacity granularity 2:  1 mWh
    model number:            42T4899
    serial number:           21064
    battery type:            LION
    OEM info:                SANYO
    Can you see how the values for "design capacity", etc., differ by a
    factor of 10 instead of 14.8 (the design voltage of this battery)?
    On the battery itself it says: 14.8V, 1.95Ah, 29Wh, so clearly the
    values reported in mWh are correct and the ones in mAh are not.
    My guess is that this problem has been around ever since those
    machines were released, but because the most common Thinkpad
    batteries are rated at 10.8V, the error (8%) is small enough that it
    simply hasn't been noticed or at least nobody could be bothered to
    look into it.
    My patch works around the problem by adjusting the incorrectly
    reported mAh values by "10000 / design_voltage".  The patch also has
    code to figure out if it should be activated or not.  It only
    activates on Lenovo Thinkpads, only when the unit is mAh, and, as an
    extra precaution, only when the battery capacity reported through
    ACPI does not match what is reported through DMI (I've never
    encountered a machine where the first two conditions would be true
    but the last would not, but better safe than sorry).
    I've been using this patch for close to a year on several systems
    without any problems.
    Acked-by: Henrique de Moraes Holschuh <>
    Signed-off-by: Rafael J. Wysocki <>
    Signed-off-by: Greg Kroah-Hartman <>
  12. @gregkh

    USB: mark uas driver as BROKEN

    gregkh committed
    commit fb37ef9 upstream.
    As reported, the UAS
    driver causes problems and has been asked to be not built into any of
    the major distributions.  To prevent users from running into problems
    with it, and for distros that were not notified, just mark the whole
    thing as broken.
    Acked-by: Sarah Sharp <>
    Signed-off-by: Greg Kroah-Hartman <>
  13. @markushx @gregkh

    USB: cp210x: add Virtenio Preon32 device id

    markushx committed with gregkh
    commit 356fe44 upstream.
    Signed-off-by: Markus Becker <>
    Signed-off-by: Greg Kroah-Hartman <>
  14. @gregkh

    usb: ftdi_sio: fixup BeagleBone A5+ quirk

    Peter Korsgaard committed with gregkh
    commit 1a88d5e upstream.
    BeagleBone A5+ devices ended up getting shipped with the
    'BeagleBone/XDS100V2' product string, and not XDS100 like it
    was agreed, so adjust the quirk to match.
    For details, see the thread on the beagle list:!msg/beagleboard/zrFPew9_Wvo/ibWr1-eE8JwJ
    Signed-off-by: Peter Korsgaard <>
    Signed-off-by: Greg Kroah-Hartman <>
  15. @tecki @gregkh

    USB: ftdi_sio: Add support for Newport AGILIS motor drivers

    tecki committed with gregkh
    commit d7e14b3 upstream.
    The Newport AGILIS model AG-UC8 compact piezo motor controller
    is yet another device using an FTDI USB-to-serial chip. It works
    fine with the ftdi_sio driver when adding
      options ftdi-sio product=0x3000 vendor=0x104d
    to modprobe.d. udevadm reports "Newport" as the manufacturer,
    and "Agilis" as the product name.
    Signed-off-by: Martin Teichmann <>
    Signed-off-by: Greg Kroah-Hartman <>
  16. @bmork @gregkh

    USB: option: blacklist network interface on Huawei E173

    bmork committed with gregkh
    commit f36446c upstream.
    The Huawei E173 will normally appear as 12d1:1436 in Linux.  But
    the modem has another mode with different device ID and a slightly
    different set of descriptors. This is the mode used by Windows like
      3Modem:      USB\VID_12D1&PID_140C&MI_00\6&3A1D2012&0&0000
      Networkcard: USB\VID_12D1&PID_140C&MI_01\6&3A1D2012&0&0001
      Appli.Inter: USB\VID_12D1&PID_140C&MI_02\6&3A1D2012&0&0002
      PC UI Inter: USB\VID_12D1&PID_140C&MI_03\6&3A1D2012&0&0003
    All interfaces have the same ff/ff/ff class codes in this mode.
    Blacklisting the network interface to allow it to be picked up by
    the network driver.
    Reported-by: Thomas Schäfer <>
    Signed-off-by: Bjørn Mork <>
    Signed-off-by: Greg Kroah-Hartman <>
  17. @gregkh

    USB: add new zte 3g-dongle's pid to option.c committed with gregkh
    commit 31b6a10 upstream.
    Signed-off-by: Rui li <>
    Signed-off-by: Greg Kroah-Hartman <>
  18. @jbeulich @gregkh

    x86: hpet: Fix masking of MSI interrupts

    jbeulich committed with gregkh
    commit 6acf5a8 upstream.
    HPET_TN_FSB is not a proper mask bit; it merely toggles between MSI and
    legacy interrupt delivery. The proper mask bit is HPET_TN_ENABLE, so
    use both bits when (un)masking the interrupt.
    Signed-off-by: Jan Beulich <>
    Signed-off-by: Thomas Gleixner <>
    Signed-off-by: Greg Kroah-Hartman <>
  19. @gregkh

    telephony: ijx: buffer overflow in ixj_write_cid()

    Dan Carpenter committed with gregkh
    [Not needed in 3.8 or newer as this driver is removed there. - gregkh]
    We get this from user space and nothing has been done to ensure that
    these strings are NUL terminated.
    Reported-by: Chen Gang <>
    Signed-off-by: Dan Carpenter <>
    Signed-off-by: Greg Kroah-Hartman <>
  20. @ostr @gregkh

    x86,AMD: Power driver support for AMD's family 16h processors

    ostr committed with gregkh
    commit 22e32f4 upstream.
    Add family 16h PCI ID to AMD's power driver to allow it report
    power consumption on these processors.
    Signed-off-by: Boris Ostrovsky <>
    Signed-off-by: Guenter Roeck <>
    Signed-off-by: Greg Kroah-Hartman <>
  21. @gregkh

    mm: dmapool: use provided gfp flags for all dma_alloc_coherent() calls

    Marek Szyprowski committed with gregkh
    commit 387870f upstream.
    dmapool always calls dma_alloc_coherent() with GFP_ATOMIC flag,
    regardless the flags provided by the caller. This causes excessive
    pruning of emergency memory pools without any good reason. Additionaly,
    on ARM architecture any driver which is using dmapools will sooner or
    later  trigger the following error:
    "ERROR: 256 KiB atomic DMA coherent pool is too small!
    Please increase it with coherent_pool= kernel parameter!".
    Increasing the coherent pool size usually doesn't help much and only
    delays such error, because all GFP_ATOMIC DMA allocations are always
    served from the special, very limited memory pool.
    This patch changes the dmapool code to correctly use gfp flags provided
    by the dmapool caller.
    Reported-by: Soeren Moch <>
    Reported-by: Thomas Petazzoni <>
    Signed-off-by: Marek Szyprowski <>
    Tested-by: Andrew Lunn <>
    Tested-by: Soeren Moch <>
    Signed-off-by: Greg Kroah-Hartman <>
  22. @jnikula @gregkh

    drm/i915: do not default to 18 bpp for eDP if missing from VBT

    jnikula committed with gregkh
    commit 9a30a61 upstream.
    commit 500a8cc
    Author: Zhenyu Wang <>
    Date:   Wed Jan 13 11:19:52 2010 +0800
        drm/i915: parse eDP panel color depth from VBT block
    originally introduced parsing bpp for eDP from VBT, with a default of 18
    bpp if the eDP BIOS data block is not present. Turns out that default seems
    to break the Macbook Pro with retina display, as noted in
    commit 4344b81
    Author: Daniel Vetter <>
    Date:   Fri Aug 10 11:10:20 2012 +0200
        drm/i915: ignore eDP bpc settings from vbt
    Since we can't ignore bpc settings from VBT completely after all, get rid
    of the default. Do not clamp eDP to 18 bpp by default if the eDP BDB is
    missing from VBT.
    Signed-off-by: Jani Nikula <>
    Tested-by: Henrik Rydberg <>
    [danvet: paste in the updated commit message from irc.]
    Signed-off-by: Daniel Vetter <>
    Signed-off-by: Greg Kroah-Hartman <>
  23. @jnikula @gregkh

    drm/i915: do not ignore eDP bpc settings from vbt

    jnikula committed with gregkh
    commit 2f4f649 upstream.
    There are laptops out there that need the eDP bpc from VBT. This is
    effectively a revert of
    commit 4344b81
    Author: Daniel Vetter <>
    Date:   Fri Aug 10 11:10:20 2012 +0200
        drm/i915: ignore eDP bpc settings from vbt
    but putting the VBT check after the EDID check to see them both in dmesg if
    this clamps more than the EDID. We have enough history with bpc clamping to
    warrant the extra debug info.
    Signed-off-by: Jani Nikula <>
    Signed-off-by: Daniel Vetter <>
    Signed-off-by: Greg Kroah-Hartman <>
  24. @gregkh

    workqueue: convert BUG_ON()s in __queue_delayed_work() to WARN_ON_ONC…

    Tejun Heo committed with gregkh
    commit fc4b514 upstream.
    8852aac ("workqueue: mod_delayed_work_on() shouldn't queue timer on
    0 delay") unexpectedly uncovered a very nasty abuse of delayed_work in
    megaraid - it allocated work_struct, casted it to delayed_work and
    then pass that into queue_delayed_work().
    Previously, this was okay because 0 @delay short-circuited to
    queue_work() before doing anything with delayed_work.  8852aac
    moved 0 @delay test into __queue_delayed_work() after sanity check on
    delayed_work making megaraid trigger BUG_ON().
    Although megaraid is already fixed by c1d390d ("megaraid: fix
    BUG_ON() from incorrect use of delayed work"), this patch converts
    BUG_ON()s in __queue_delayed_work() to WARN_ON_ONCE()s so that such
    abusers, if there are more, trigger warning but don't crash the
    Signed-off-by: Tejun Heo <>
    Cc: Xiaotian Feng <>
    Signed-off-by: Shuah Khan <>
    Signed-off-by: Greg Kroah-Hartman <>
  25. @ujfalusi @gregkh

    ASoC: dmaengine: Correct Makefile when sound is built as module

    ujfalusi committed with gregkh
    commit 961a7ae upstream.
    soc-dmaengine-pcm library need to be part of the snd-soc-core in order to
    be able to compile ASoC as modules when dmaengine is enabled on the platform.
    Signed-off-by: Peter Ujfalusi <>
    Signed-off-by: Mark Brown <>
    Cc: Florian Fainelli <>
    Signed-off-by: Greg Kroah-Hartman <>
  26. @gregkh

    ARM: 7566/1: vfp: fix save and restore when running on pre-VFPv3 and …

    Paul Walmsley committed with gregkh
    …CONFIG_VFPv3 set
    commit 39141dd upstream.
    After commit 846a136 ("ARM: vfp: fix
    saving d16-d31 vfp registers on v6+ kernels"), the OMAP 2430SDP board
    started crashing during boot with omap2plus_defconfig:
    [    3.875122] mmcblk0: mmc0:e624 SD04G 3.69 GiB
    [    3.915954]  mmcblk0: p1
    [    4.086639] Internal error: Oops - undefined instruction: 0 [#1] SMP ARM
    [    4.093719] Modules linked in:
    [    4.096954] CPU: 0    Not tainted  (3.6.0-02232-g759e00b #570)
    [    4.103149] PC is at vfp_reload_hw+0x1c/0x44
    [    4.107666] LR is at __und_usr_fault_32+0x0/0x8
    It turns out that the context save/restore fix unmasked a latent bug
    in commit 5aaf254 ("ARM: 6203/1: Make
    VFPv3 usable on ARMv6").  When CONFIG_VFPv3 is set, but the kernel is
    booted on a pre-VFPv3 core, the code attempts to save and restore the
    d16-d31 VFP registers.  These are only present on non-D16 VFPv3+, so
    this results in an undefined instruction exception.  The code didn't
    crash before commit 846a136 because the save and restore code was
    only touching d0-d15, present on all VFP.
    Fix by implementing a request from Russell King to add a new HWCAP
    flag that affirmatively indicates the presence of the d16-d31
    and some feedback from Måns to clarify the name of the HWCAP flag.
    Signed-off-by: Paul Walmsley <>
    Cc: Tony Lindgren <>
    Cc: Catalin Marinas <>
    Cc: Dave Martin <>
    Cc: Måns Rullgård <>
    Signed-off-by: Russell King <>
    Cc: Ben Hutchings <>
    Signed-off-by: Greg Kroah-Hartman <>
  27. @lyakh @gregkh

    mmc: sh-mmcif: avoid oops on spurious interrupts (second try)

    lyakh committed with gregkh
    commit 91ab252 upstream.
    On some systems, e.g., kzm9g, MMCIF interfaces can produce spurious
    interrupts without any active request. To prevent the Oops, that results
    in such cases, don't dereference the mmc request pointer until we make
    sure, that we are indeed processing such a request.
    Reported-by: Tetsuyuki Kobayashi <>
    Signed-off-by: Guennadi Liakhovetski <>
    Tested-by: Tetsuyuki Kobayashi <>
    Signed-off-by: Chris Ball <>
    Signed-off-by: Greg Kroah-Hartman <>
  28. @cjb @gregkh

    Revert misapplied "mmc: sh-mmcif: avoid oops on spurious interrupts"

    cjb committed with gregkh
    commit 6984f3c upstream.
    This reverts commit 8464dd5, which was a misapplied debugging
    version of the patch, not the final patch itself.
    Signed-off-by: Chris Ball <>
    Signed-off-by: Greg Kroah-Hartman <>
  29. @gregkh

    tmpfs: fix shared mempolicy leak

    Mel Gorman committed with gregkh
    commit 18a2f37 upstream.
    This fixes a regression in 3.7-rc, which has since gone into stable.
    Commit 00442ad ("mempolicy: fix a memory corruption by refcount
    imbalance in alloc_pages_vma()") changed get_vma_policy() to raise the
    refcount on a shmem shared mempolicy; whereas shmem_alloc_page() went
    on expecting alloc_page_vma() to drop the refcount it had acquired.
    This deserves a rework: but for now fix the leak in shmem_alloc_page().
    Hugh: shmem_swapin() did not need a fix, but surely it's clearer to use
    the same refcounting there as in shmem_alloc_page(), delete its onstack
    mempolicy, and the strange mpol_cond_copy() and __mpol_cond_copy() -
    those were invented to let swapin_readahead() make an unknown number of
    calls to alloc_pages_vma() with one mempolicy; but since 00442ad,
    alloc_pages_vma() has kept refcount in balance, so now no problem.
    Reported-and-tested-by: Tommi Rantala <>
    Signed-off-by: Mel Gorman <>
    Signed-off-by: Hugh Dickins <>
    Signed-off-by: Linus Torvalds <>
    Signed-off-by: Greg Kroah-Hartman <>
Commits on Dec 10, 2012
  1. @gregkh

    Linux 3.4.23

    gregkh committed
  2. @michal42 @gregkh

    kbuild: Do not package /boot and /lib in make tar-pkg

    michal42 committed with gregkh
    commit fe04ddf upstream.
    There were reports of users destroying their Fedora installs by a kernel
    tarball that replaces the /lib -> /usr/lib symlink. Let's remove the
    toplevel directories from the tarball to prevent this from happening.
    Reported-by: Andi Kleen <>
    Suggested-by: Ben Hutchings <>
    Signed-off-by: Michal Marek <>
    [bwh: Fold in commit 3ce9e53 to avoid
    Signed-off-by: Ben Hutchings <>
    Signed-off-by: Greg Kroah-Hartman <>
  3. @bergwolf @gregkh

    pnfsblock: fix partial page buffer wirte

    bergwolf committed with gregkh
    commit fe6e1e8 upstream.
    If applications use flock to protect its write range, generic NFS
    will not do read-modify-write cycle at page cache level. Therefore
    LD should know how to handle non-sector aligned writes. Otherwise
    there will be data corruption.
    Signed-off-by: Peng Tao <>
    Signed-off-by: Trond Myklebust <>
    Signed-off-by: Greg Kroah-Hartman <>
  4. @ickle @gregkh

    drm/i915: Add no-lvds quirk for Supermicro X7SPA-H

    ickle committed with gregkh
    commit c31407a upstream.
    Reported-and-tested-by: Francois Tigeot <>
    Signed-off-by: Chris Wilson <>
    Signed-off-by: Daniel Vetter <>
    Signed-off-by: Peter Huewe <>
    Signed-off-by: Greg Kroah-Hartman <>
  5. @kepstin @gregkh

    i915: Quirk no_lvds on Gigabyte GA-D525TUD ITX motherboard

    kepstin committed with gregkh
    commit a51d4ed upstream.
    This board is incorrectly detected as having an LVDS connector,
    resulting in the VGA output (the only available output on the board)
    showing the console only in the top-left 1024x768 pixels, and an extra
    LVDS connector appearing in X.
    It's a desktop Mini-ITX board using an Atom D525 CPU with an NM10
    I've had this board for about a year, but this is the first time I
    noticed the issue because I've been running it headless for most of its
    Signed-off-by: Calvin Walton <>
    Signed-off-by: Peter Huewe <>
    Signed-off-by: Greg Kroah-Hartman <>
  6. @gregkh

    ACPI: missing break

    Alan Cox committed with gregkh
    commit 879dca0 upstream.
    We handle NOTIFY_THROTTLING so don't then fall through to unsupported event.
    Signed-off-by: Alan Cox <>
    Signed-off-by: Rafael J. Wysocki <>
    Signed-off-by: Peter Huewe <>
    Signed-off-by: Greg Kroah-Hartman <>
Something went wrong with that request. Please try again.