Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Jun 4, 2012
  1. Merge branch 'configs-3.4' into pf-3.4

    Oleksandr Natalenko authored
  2. configs-3.4: update actual configs

    Oleksandr Natalenko authored
  3. fix merge conflict

    Oleksandr Natalenko authored
  4. Merge branch 'configs-3.4' into pf-3.4

    Oleksandr Natalenko authored
  5. Merge branch 'configs-3.4' into pf-3.4

    Oleksandr Natalenko authored
  6. configs-3.4: update config for Dell Inspiron 1525 laptop

    Oleksandr Natalenko authored
    This commit removes deprecated /proc ACPI entries and introduces DebugFS
    as well as tracing support for PowerTOP handling.
Commits on Jun 3, 2012
  1. Merge branch 'configs-3.4' into pf-3.4

    Oleksandr Natalenko authored
  2. configs-3.4: update config for Dell Inspiron 1525 laptop

    Oleksandr Natalenko authored
  3. Merge branch 'layer7-3.4' into pf-3.4

    Oleksandr Natalenko authored
  4. Merge branch 'imq-3.4' into pf-3.4

    Oleksandr Natalenko authored
  5. imq-3.4: add forgotten symbol export

    Oleksandr Natalenko authored
  6. Merge branch 'imq-3.4' into pf-3.4

    Oleksandr Natalenko authored
  7. imq-3.4: port LinuxIMQ for Linux v3.4 from DD-WRT source tree

    Oleksandr Natalenko authored
Commits on Jun 2, 2012
  1. Merge branch 'ck-3.4' into pf-3.4

    Oleksandr Natalenko authored
  2. ck-3.4: merge -ck for Linux 3.4

    Oleksandr Natalenko authored
Commits on Jun 1, 2012
  1. @NigelCunningham

    Reset I/O thread affinity before starting work.

    NigelCunningham authored
    Eureka! The source of those pesky -22 (-EINVAL) resume-time failures
    to read an image has (I hope!) finally been solved: at CPU hotplug
    time, affinities for the threads are broken, making it possible for
    them to stomp over each others' data. This doesn't seem to be very
    common on the vanilla scheduler (the error was impossible to reliably
    reproduce). On the BFS scheduler, however, it was perfectly reliably
    reproducible (thanks, Con!).
    
    While addressing this issue, I also tidied the code path in the
    compression code's page writing function.
    
    Signed-off-by: Nigel Cunningham <nigel@tuxonice.net>
  2. @gregkh

    Linux 3.4.1

    gregkh authored
  3. @gregkh

    i2c: tegra: notify transfer-complete after clearing status.

    Laxman Dewangan authored gregkh committed
    commit c889e91 upstream.
    
    The notification of the transfer complete by calling complete()
    should be done after clearing all interrupt status.
    This avoids the race condition of misconfigure the i2c controller
    in multi-core environment.
    
    Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
    Acked-by: Stephen Warren <swarren@wwwdotorg.org>
    Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  4. @marcusfolkesson @gregkh

    i2c: davinci: Free requested IRQ in remove

    marcusfolkesson authored gregkh committed
    commit 9868a06 upstream.
    
    The freed IRQ is not necessary the one requested in probe.
    Even if it was, with two or more i2c-controllers it will fails anyway.
    
    Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
    Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  5. @gregkh

    MCE: Fix vm86 handling for 32bit mce handler

    Andi Kleen authored gregkh committed
    commit a129a7c upstream.
    
    When running on 32bit the mce handler could misinterpret
    vm86 mode as ring 0. This can affect whether it does recovery
    or not; it was possible to panic when recovery was actually
    possible.
    
    Fix this by always forcing vm86 to look like ring 3.
    
    Signed-off-by: Andi Kleen <ak@linux.intel.com>
    Signed-off-by: Tony Luck <tony.luck@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  6. @swarren @gregkh

    ARM: dt: tegra cardhu: fix typo in SDHCI node name

    swarren authored gregkh committed
    commit 1dfebb4 upstream.
    
    Cardhu's eMMC controller is on sdhci@7800060, not sdhci@7800040.
    Fix the typo. This roughly doubles the IO performance, since the
    support-8bit property actually takes effect.
    
    Signed-off-by: Stephen Warren <swarren@nvidia.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  7. @gregkh

    ARM: 7409/1: Do not call flush_cache_user_range with mmap_sem held

    Dima Zavin authored gregkh committed
    commit 435a7ef upstream.
    
    We can't be holding the mmap_sem while calling flush_cache_user_range
    because the flush can fault. If we fault on a user address, the
    page fault handler will try to take mmap_sem again. Since both places
    acquire the read lock, most of the time it succeeds. However, if another
    thread tries to acquire the write lock on the mmap_sem (e.g. mmap) in
    between the call to flush_cache_user_range and the fault, the down_read
    in do_page_fault will deadlock.
    
    [will: removed drop of vma parameter as already queued by rmk (7365/1)]
    
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Dima Zavin <dima@android.com>
    Signed-off-by: John Stultz <john.stultz@linaro.org>
    Signed-off-by: Will Deacon <will.deacon@arm.com>
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  8. @gregkh

    ARM: 7365/1: drop unused parameter from flush_cache_user_range

    Dima Zavin authored gregkh committed
    commit 4542b6a upstream.
    
    vma isn't used and flush_cache_user_range isn't a standard macro that
    is used on several archs with the same prototype. In fact only unicore32
    has a macro with the same name (with an identical implementation and no
    in-tree users).
    
    This is a part of a patch proposed by Dima Zavin (with Message-id:
    1272439931-12795-1-git-send-email-dima@android.com) that didn't get
    accepted.
    
    Cc: Dima Zavin <dima@android.com>
    Acked-by: Catalin Marinas <catalin.marinas@arm.com>
    Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Cc: Will Deacon <will.deacon@arm.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  9. @gregkh

    iommu: Fix off by one in dmar_get_fault_reason()

    Dan Carpenter authored gregkh committed
    commit fefe1ed upstream.
    
    fault_reason - 0x20 == ARRAY_SIZE(irq_remap_fault_reasons) is
    one past the end of the array.
    
    Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
    Cc: Joerg Roedel <joerg.roedel@amd.com>
    Cc: Youquan Song <youquan.song@intel.com>
    Cc: walter harms <wharms@bfs.de>
    Cc: Suresh Siddha <suresh.b.siddha@intel.com>
    Link: http://lkml.kernel.org/r/20120513170938.GA4280@elgon.mountain
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    [bwh: Backported to 3.2: s/irq_remap_fault_reasons/intr_remap_fault_reasons/]
    Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  10. @dwmw2 @gregkh

    intel-iommu: Add device info into list before doing context mapping

    dwmw2 authored gregkh committed
    commit e2ad23d upstream.
    
    Add device info into list before doing context mapping, because device
    info will be used by iommu_enable_dev_iotlb(). Without it, ATS won't get
    enabled as it should be.
    
    ATS, while a dubious decision from a security point of view, can be very
    important for performance.
    
    Signed-off-by: Xudong Hao <xudong.hao@intel.com>
    Signed-off-by: Xiantao Zhang <xiantao.zhang@intel.com>
    Acked-by: Chris Wright <chrisw@sous-sol.org>
    Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  11. @cmetcalf-tilera @gregkh

    tile: fix bug where fls(0) was not returning 0

    cmetcalf-tilera authored gregkh committed
    commit 9f1d62b upstream.
    
    This is because __builtin_clz(0) returns 64 for the "undefined" case
    of 0, since the builtin just does a right-shift 32 and "clz" instruction.
    So, use the alpha approach of casting to u32 and using __builtin_clzll().
    
    Signed-off-by: Chris Metcalf <cmetcalf@tilera.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  12. @gregkh

    mmc: omap_hsmmc: pass IRQF_ONESHOT to request_threaded_irq

    Ming Lei authored gregkh committed
    commit db35f83 upstream.
    
    The flag of IRQF_ONESHOT should be passed to request_threaded_irq,
    otherwise the following failure message should be dumped because
    hardware handler is defined as NULL:
    
    [    3.383483] genirq: Threaded irq requested with handler=NULL and
    !ONESHOT for irq 368
    [    3.392730] omap_hsmmc: probe of omap_hsmmc.0 failed with error -22
    
    The patch fixes one kernel hang bug which is caused by mmc card
    probe failure and root device can't be brought up.
    
    Signed-off-by: Ming Lei <ming.lei@canonical.com>
    Acked-by: Venkatraman S <svenkatr@ti.com>
    Signed-off-by: Chris Ball <cjb@laptop.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  13. @lyakh @gregkh

    mmc: cd-gpio: protect against NULL context in mmc_cd_gpio_free()

    lyakh authored gregkh committed
    commit 0e9f480 upstream.
    
    Do not oops, even if mmc_cd_gpio_free() is mistakenly called on a driver
    cleanup path, even though a previous call to mmc_cd_gpio_request() failed.
    
    Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
    [stable@: please apply to 3.3-stable]
    Signed-off-by: Chris Ball <cjb@laptop.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  14. @gregkh

    mmc: sdio: avoid spurious calls to interrupt handlers

    Nicolas Pitre authored gregkh committed
    commit bbbc4c4 upstream.
    
    Commit 06e8935 ("optimized SDIO IRQ handling for single irq")
    introduced some spurious calls to SDIO function interrupt handlers,
    such as when the SDIO IRQ thread is started, or the safety check
    performed upon a system resume.  Let's add a flag to perform the
    optimization only when a real interrupt is signaled by the host
    driver and we know there is no point confirming it.
    
    Reported-by: Sujit Reddy Thumma <sthumma@codeaurora.org>
    Signed-off-by: Nicolas Pitre <nico@linaro.org>
    Signed-off-by: Chris Ball <cjb@laptop.org>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  15. @gregkh

    x86/mce: Fix check for processor context when machine check was taken.

    Tony Luck authored gregkh committed
    commit 875e266 upstream.
    
    Linus pointed out that there was no value is checking whether m->ip
    was zero - because zero is a legimate value.  If we have a reliable
    (or faked in the VM86 case) "m->cs" we can use it to tell whether we
    were in user mode or kernelwhen the machine check hit.
    
    Reported-by: Linus Torvalds <torvalds@linuxfoundation.org>
    Signed-off-by: Tony Luck <tony.luck@intel.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  16. @gregkh

    x86, relocs: Add jiffies and jiffies_64 to the relative whitelist

    H. Peter Anvin authored gregkh committed
    commit ea17e74 upstream.
    
    The symbol jiffies is created in the linker script as an alias to
    jiffies_64.  Unfortunately this is done outside any section, and
    apparently GNU ld 2.21 doesn't carry the section with it, so we end up
    with an absolute symbol and therefore a broken kernel.
    
    Add jiffies and jiffies_64 to the whitelist.
    
    The most disturbing bit with this discovery is that it shows that we
    have had multiple linker bugs in this area crossing multiple
    generations, and have been silently building bad kernels for some time.
    
    Link: http://lkml.kernel.org/r/20120524171604.0d98284f3affc643e9714470@canb.auug.org.au
    Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
    Signed-off-by: H. Peter Anvin <hpa@zytor.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  17. @gregkh

    x86-32, relocs: Whitelist more symbols for ld bug workaround

    H. Peter Anvin authored gregkh committed
    commit fd95281 upstream.
    
    As noted in checkin:
    
    a3e854d x86, relocs: Workaround for binutils 2.22.52.0.1 section bug
    
    ld version 2.22.52.0.[12] can incorrectly promote relative symbols to
    absolute, if the output section they appear in is otherwise empty.
    
    Since checkin:
    
    6520fe5 x86, realmode: 16-bit real-mode code support for relocs tool
    
    we actually check for this and error out rather than silently creating
    a kernel which will malfunction if relocated.
    
    Ingo found a configuration in which __start_builtin_fw triggered the
    warning.
    
    Go through the linker script sources and look for more symbols that
    could plausibly get bogusly promoted to absolute, and add them to the
    whitelist.
    
    In general, if the following error triggers:
    
    	Invalid absolute R_386_32 relocation: <symbol>
    
    ... then we should verify that <symbol> is really meant to be
    relocated, and add it and any related symbols manually to the S_REL
    regexp.
    
    Please note that 6520fe5 does not introduce the error, only the check
    for the error -- without 6520fe5 this version of ld will simply
    produce a corrupt kernel if CONFIG_RELOCATABLE is set on x86-32.
    
    Reported-by: Ingo Molnar <mingo@kernel.org>
    Signed-off-by: H. Peter Anvin <hpa@zytor.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Something went wrong with that request. Please try again.