Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Commits on Apr 2, 2009
  1. @chriswright

    Linux 2.6.29.1

    chriswright authored
  2. @chriswright

    V4L: v4l2-common: remove incorrect MODULE test

    Hans Verkuil authored chriswright committed
    upstream commit: d64260d
    
    v4l2-common doesn't have to be a module for it to call request_module().
    Just remove that test.
    
    Without this patch loading ivtv as a module while v4l2-common is compiled
    into the kernel will cause a delayed load of the i2c modules that ivtv
    needs since request_module is never called directly.
    
    While it is nice to see the delayed load in action, it is not so nice in
    that ivtv fails to do a lot of necessary i2c initializations and will oops
    later on with a division-by-zero.
    
    Thanks to Mark Lord for reporting this and helping me figure out what was
    wrong.
    
    Thanks-to: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
    Thanks-to: Mark Lord <lkml@rtr.ca>
    Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
    Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
    Signed-off-by: Michael Krufky <mkrufky@linuxtv.org>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  3. @davem330 @chriswright

    sparc64: Fix reset hangs on Niagara systems.

    davem330 authored chriswright committed
    [ Upstream commit ffaba67 ]
    
    Hypervisor versions older than version 1.6.1 cannot handle
    leaving the profile counter overflow interrupt chirping
    when the system does a soft reset.
    
    So use a reboot notifier to shut off the NMI watchdog.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  4. @davem330 @chriswright

    sparc64: Flush TLB before releasing pages.

    davem330 authored chriswright committed
    [ Upstream commit a552a42cfa91ab653128dff89a70c8dde7fed042 ]
    
    tlb_flush_mmu() needs to flush pending TLB entries before
    processing the mmu_gather ->pages list.
    
    Noticed by Benjamin Herrenschmidt.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  5. @davem330 @chriswright

    sparc64: Fix MM refcount check in smp_flush_tlb_pending().

    davem330 authored chriswright committed
    [ Upstream commit f9384d4 ]
    
    As explained by Benjamin Herrenschmidt:
    
    > CPU 0 is running the context, task->mm == task->active_mm == your
    > context. The CPU is in userspace happily churning things.
    >
    > CPU 1 used to run it, not anymore, it's now running fancyfsd which
    > is a kernel thread, but current->active_mm still points to that
    > same context.
    >
    > Because there's only one "real" user, mm_users is 1 (but mm_count is
    > elevated, it's just that the presence on CPU 1 as active_mm has no
    > effect on mm_count().
    >
    > At this point, fancyfsd decides to invalidate a mapping currently mapped
    > by that context, for example because a networked file has changed
    > remotely or something like that, using unmap_mapping_ranges().
    >
    > So CPU 1 goes into the zapping code, which eventually ends up calling
    > flush_tlb_pending(). Your test will succeed, as current->active_mm is
    > indeed the target mm for the flush, and mm_users is indeed 1. So you
    > will -not- send an IPI to the other CPU, and CPU 0 will continue happily
    > accessing the pages that should have been unmapped.
    
    To fix this problem, check ->mm instead of ->active_mm, and this
    means:
    
    > So if you test current->mm, you effectively account for mm_users == 1,
    > so the only way the mm can be active on another processor is as a lazy
    > mm for a kernel thread. So your test should work properly as long
    > as you don't have a HW that will do speculative TLB reloads into the
    > TLB on that other CPU (and even if you do, you flush-on-switch-in should
    > get rid of any crap here).
    
    And therefore we should be OK.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  6. @chriswright

    KVM: MMU: Fix another largepage memory leak

    Joerg Roedel authored chriswright committed
    upstream commit: c5bc224
    
    In the paging_fetch function rmap_remove is called after setting a large
    pte to non-present. This causes rmap_remove to not drop the reference to
    the large page. The result is a memory leak of that page.
    
    Cc: stable@kernel.org
    Signed-off-by: Joerg Roedel <joerg.roedel@amd.com>
    Acked-by: Marcelo Tosatti <mtosatti@redhat.com>
    Signed-off-by: Avi Kivity <avi@redhat.com>
    [chrisw: backport to 2.6.29]
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  7. @chriswright

    cfg80211: fix incorrect assumption on last_request for 11d

    Luis R. Rodriguez authored chriswright committed
    upstream commit: cc0b6fe
    
    The incorrect assumption is the last regulatory request
    (last_request) is always a country IE when processing
    country IEs. Although this is true 99% of the time the
    first time this happens this could not be true.
    
    This fixes an oops in the branch check for the last_request
    when accessing drv_last_ie. The access was done under the
    assumption the struct won't be null.
    
    Note to stable: to port to 29 replace as follows, only 29 has
    country IE code:
    
    s|NL80211_REGDOM_SET_BY_COUNTRY_IE|REGDOM_SET_BY_COUNTRY_IE
    
    Cc: stable@kernel.org
    Reported-by: Quentin Armitage <Quentin@armitage.org.uk>
    Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    [chrisw: backport to 2.6.29]
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  8. @rustyrussell @chriswright

    lguest: fix spurious BUG_ON() on invalid guest stack.

    rustyrussell authored chriswright committed
    upstream commit: 6afbdd0
    
    Impact: fix crash on misbehaving guest
    
    gpte_addr() contains a BUG_ON(), insisting that the present flag is
    set.  We need to return before we call it if that isn't the case.
    
    Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
    Cc: stable@kernel.org
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  9. @rustyrussell @chriswright

    lguest: wire up pte_update/pte_update_defer

    rustyrussell authored chriswright committed
    upstream commit: b7ff99e
    
    Impact: intermittent guest segv/crash fix
    
    I've been seeing random guest bad address crashes and segmentation faults:
    bisect led to 4f98a2f (vmscan: split LRU lists into anon & file sets),
    but that's a red herring.
    
    It turns out that lguest never hooked up the pte_update/pte_update_defer
    calls, so our ptes were not always in sync.  After the vmscan commit, the
    bug became reproducible; now a fsck in a 64MB guest causes reproducible
    pagetable corruption.
    
    Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
    Cc: jeremy@xensource.com
    Cc: virtualization@lists.osdl.org
    Cc: stable@kernel.org
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  10. @chriswright

    VM, x86, PAT: Change is_linear_pfn_mapping to not use vm_pgoff

    Pallipadi, Venkatesh authored chriswright committed
    upstream commit: 4bb9c5c
    
    Impact: fix false positive PAT warnings - also fix VirtalBox hang
    
    Use of vma->vm_pgoff to identify the pfnmaps that are fully
    mapped at mmap time is broken. vm_pgoff is set by generic mmap
    code even for cases where drivers are setting up the mappings
    at the fault time.
    
    The problem was originally reported here:
    
     http://marc.info/?l=linux-kernel&m=123383810628583&w=2
    
    Change is_linear_pfn_mapping logic to overload VM_INSERTPAGE
    flag along with VM_PFNMAP to mean full PFNMAP setup at mmap
    time.
    
    Problem also tracked at:
    
     http://bugzilla.kernel.org/show_bug.cgi?id=12800
    
    Reported-by: Thomas Hellstrom <thellstrom@vmware.com>
    Tested-by: Frans Pop <elendil@planet.nl>
    Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
    Cc: Nick Piggin <npiggin@suse.de>
    Cc: "ebiederm@xmission.com" <ebiederm@xmission.com>
    Cc: <stable@kernel.org> # only for 2.6.29.1, not .28
    LKML-Reference: <20090313004527.GA7176@linux-os.sc.intel.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  11. @chriswright

    x86: mtrr: don't modify RdDram/WrDram bits of fixed MTRRs

    Andreas Herrmann authored chriswright committed
    upstream commit: 3ff42da
    
    Impact: bug fix + BIOS workaround
    
    BIOS is expected to clear the SYSCFG[MtrrFixDramModEn] on AMD CPUs
    after fixed MTRRs are configured.
    
    Some BIOSes do not clear SYSCFG[MtrrFixDramModEn] on BP (and on APs).
    
    This can lead to obfuscation in Linux when this bit is not cleared on
    BP but cleared on APs. A consequence of this is that the saved
    fixed-MTRR state (from BP) differs from the fixed-MTRRs of APs --
    because RdDram/WrDram bits are read as zero when
    SYSCFG[MtrrFixDramModEn] is cleared -- and Linux tries to sync
    fixed-MTRR state from BP to AP. This implies that Linux sets
    SYSCFG[MtrrFixDramEn] and activates those bits.
    
    More important is that (some) systems change these bits in SMM when
    ACPI is enabled. Hence it is racy if Linux modifies RdMem/WrMem bits,
    too.
    
    (1) The patch modifies an old fix from Bernhard Kaindl to get
        suspend/resume working on some Acer Laptops. Bernhard's patch
        tried to sync RdMem/WrMem bits of fixed MTRR registers and that
        helped on those old Laptops. (Don't ask me why -- can't test it
        myself). But this old problem was not the motivation for the
        patch. (See http://lkml.org/lkml/2007/4/3/110)
    
    (2) The more important effect is to fix issues on some more current systems.
    
        On those systems Linux panics or just freezes, see
    
        http://bugzilla.kernel.org/show_bug.cgi?id=11541
        (and also duplicates of this bug:
        http://bugzilla.kernel.org/show_bug.cgi?id=11737
        http://bugzilla.kernel.org/show_bug.cgi?id=11714)
    
        The affected systems boot only using acpi=ht, acpi=off or
        when the kernel is built with CONFIG_MTRR=n.
    
        The acpi options prevent full enablement of ACPI.  Obviously when
        ACPI is enabled the BIOS/SMM modfies RdMem/WrMem bits.  When
        CONFIG_MTRR=y Linux also accesses and modifies those bits when it
        needs to sync fixed-MTRRs across cores (Bernhard's fix, see (1)).
        How do you synchronize that? You can't. As a consequence Linux
        shouldn't touch those bits at all (Rationale are AMD's BKDGs which
        recommend to clear the bit that makes RdMem/WrMem accessible).
        This is the purpose of this patch. And (so far) this suffices to
        fix (1) and (2).
    
    I suggest not to touch RdDram/WrDram bits of fixed-MTRRs and
    SYSCFG[MtrrFixDramEn] and to clear SYSCFG[MtrrFixDramModEn] as
    suggested by AMD K8, and AMD family 10h/11h BKDGs.
    BIOS is expected to do this anyway. This should avoid that
    Linux and SMM tread on each other's toes ...
    
    Signed-off-by: Andreas Herrmann <andreas.herrmann3@amd.com>
    Cc: trenn@suse.de
    Cc: Yinghai Lu <yinghai@kernel.org>
    LKML-Reference: <20090312163937.GH20716@alberich.amd.com>
    Cc: <stable@kernel.org>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  12. @congwang @chriswright

    x86: ptrace, bts: fix an unreachable statement

    congwang authored chriswright committed
    upstream commit: 5a8ac9d
    
    Commit c272477 put a statement
    after return, which makes that statement unreachable.
    
    Move that statement before return.
    
    Signed-off-by: WANG Cong <xiyou.wangcong@gmail.com>
    Cc: Roland McGrath <roland@redhat.com>
    Cc: Markus Metzger <markus.t.metzger@intel.com>
    LKML-Reference: <20090313075622.GB8933@hack>
    Cc: <stable@kernel.org> # .29 only
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  13. @chriswright

    x86: fix 64k corruption-check

    Yinghai Lu authored chriswright committed
    upstream commit: 6d7942d
    
    Impact: fix boot crash
    
    Need to exit early if the addr is far above 64k.
    
    The crash got exposed by:
    
      78a8b35: x86: make e820_update_range() handle small range update
    
    Signed-off-by: Yinghai Lu <yinghai@kernel.org>
    Cc: <stable@kernel.org>
    LKML-Reference: <49BC2279.2030101@kernel.org>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  14. @rustyrussell @chriswright

    x86, uv: fix cpumask iterator in uv_bau_init()

    rustyrussell authored chriswright committed
    upstream commit: 2c74d66
    
    Impact: fix boot crash on UV systems
    
    Commit 76ba0ec "cpumask: use
    cpumask_var_t in uv_flush_tlb_others" used cur_cpu as an iterator;
    it was supposed to be zero for the code below it.
    
    Reported-by: Cliff Wickman <cpw@sgi.com>
    Original-From: Cliff Wickman <cpw@sgi.com>
    Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
    Acked-by: Mike Travis <travis@sgi.com>
    Cc: steiner@sgi.com
    Cc: <stable@kernel.org>
    LKML-Reference: <200903180822.31196.rusty@rustcorp.com.au>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  15. @chriswright

    x86, PAT, PCI: Change vma prot in pci_mmap to reflect inherited prot

    Pallipadi, Venkatesh authored chriswright committed
    upstream commit: 9cdec04
    
    While looking at the issue in the thread:
    
      http://marc.info/?l=dri-devel&m=123606627824556&w=2
    
    noticed a bug in pci PAT code and memory type setting.
    
    PCI mmap code did not set the proper protection in vma, when it
    inherited protection in reserve_memtype. This bug only affects
    the case where there exists a WC mapping before X does an mmap
    with /proc or /sys pci interface. This will cause X userlevel
    mmap from /proc or /sysfs to fail on fork.
    
    Reported-by: Kevin Winchester <kjwinchester@gmail.com>
    Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
    Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>
    Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
    Cc: Dave Airlie <airlied@redhat.com>
    Cc: <stable@kernel.org>
    LKML-Reference: <20090323190720.GA16831@linux-os.sc.intel.com>
    Signed-off-by: Ingo Molnar <mingo@elte.hu>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  16. @error27 @chriswright

    Add a missing unlock_kernel() in raw_open()

    error27 authored chriswright committed
    upstream commit: 996ff68
    
    Cc: stable@kernel.org
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: Jonathan Corbet <corbet@lwn.net>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  17. @error27 @chriswright

    fuse: fix fuse_file_lseek returning with lock held

    error27 authored chriswright committed
    upstream commit: 5291658
    
    This bug was found with smatch (http://repo.or.cz/w/smatch.git/).  If
    we return directly the inode->i_mutex lock doesn't get released.
    
    Signed-off-by: Dan Carpenter <error27@gmail.com>
    Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
    CC: stable@kernel.org
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  18. @chriswright

    ARM: 5435/1: fix compile warning in sanity_check_meminfo()

    Mikael Pettersson authored chriswright committed
    upstream commit: f0bba9f
    
    Compiling recent 2.6.29-rc kernels for ARM gives me the following warning:
    
    arch/arm/mm/mmu.c: In function 'sanity_check_meminfo':
    arch/arm/mm/mmu.c:697: warning: comparison between pointer and integer
    
    This is because commit 3fd9825
    "[ARM] 5402/1: fix a case of wrap-around in sanity_check_meminfo()"
    in 2.6.29-rc5-git4 added a comparison of a pointer with PAGE_OFFSET,
    which is an integer.
    
    Fixed by casting PAGE_OFFSET to void *.
    
    Signed-off-by: Mikael Pettersson <mikpe@it.uu.se>
    Acked-by: Nicolas Pitre <nico@cam.org>
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  19. @Alan-Cox @chriswright

    ARM: twl4030 - leak fix

    Alan-Cox authored chriswright committed
    upstream commit: 803c78e
    
    Trivial error path leak fix. Problem found by Daniel Marjamäki using
    cppcheck
    
    Signed-off-by: Alan Cox <alan@lxorguk.ukuu.org.uk>
    Acked-by: Tony Lindgren <tony@atomide.com>
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  20. @Alan-Cox @chriswright

    ARM: fix leak in iop13xx/pci

    Alan-Cox authored chriswright committed
    upstream commit: b23c7a4
    
    Another leak found by Daniel Marjamäki
    
    Signed-off-by: Alan Cox <alan@lxorguk.ukuu.org.uk>
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  21. @Alan-Cox @chriswright

    ARM: cumana: Fix a long standing bogon

    Alan-Cox authored chriswright committed
    upstream commit: ecbf61e
    
    Should be using strncmp as the data from user space may be unterminated
    
    (Bug #8004)
    
    Signed-off-by: Alan Cox <alan@lxorguk.ukuu.org.uk
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  22. @chriswright

    ARM: 5428/1: Module relocation update for R_ARM_V4BX

    Daniel Silverstone authored chriswright committed
    upstream commit: 4731f8b
    
    It would seem when building kernel modules with modern binutils
    (required by modern GCC) for ARM v4T targets (specifically observed
    with the Samsung 24xx SoC which is an 920T) R_ARM_V4BX relocations
    are emitted for function epilogues.
    
    This manifests at module load time with an "unknown relocation: 40"
    error message.
    
    The following patch adds the R_ARM_V4BX relocation to the ARM kernel
    module loader. The relocation operation is taken from that within the
    binutils bfd library.
    
    Signed-off-by: Simtec Linux Team <linux@simtec.co.uk>
    Signed-off-by: Vincent Sanders <vince@simtec.co.uk>
    Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  23. @chriswright

    ARM: pxa: fix overlay being un-necessarily initialized on pxa25x

    Eric Miao authored chriswright committed
    upstream commit: 782385a
    
    pxa25x doesn't support overlay in its LCD controller, this patch adds
    pxafb_overlay_supported() functions to check the initialization is
    necessary.
    
    Signed-off-by: Eric Miao <eric.miao@marvell.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  24. @chriswright

    DVB: firedtv: FireDTV S2 problems with tuning solved

    Beat Michel Liechti authored chriswright committed
    upstream commit: 32a0f48
    
    Tuning was broken on FireDTV S2 (and presumably  FloppyDTV S2) because a
    wrong opcode was sent.  The box only gave "not implemented" responses.
    Changing the opcode to _TUNE_QPSK2 fixes this for good.
    
    Cc: stable@kernel.org
    Signed-off-by: Beat Michel Liechti <bml303@gmail.com>
    Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  25. @chriswright

    cfg80211: force last_request to be set for OLD_REG if regdom is EU

    Luis R. Rodriguez authored chriswright committed
    upstream commit: 2e097dc
    
    Although EU is a bogus alpha2 we need to process the send request
    as our code depends on last_request being set.
    
    Cc: stable@kernel.org
    Reported-by: Quentin Armitage <Quentin@armitage.org.uk>
    Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    [chrisw: backport to 2.6.29]
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
    Port-acked-by: Luis R. Rodriguez <lrodriguez@atheros.com>
  26. @chriswright

    CIFS: Fix memory overwrite when saving nativeFileSystem field during …

    Steve French authored chriswright committed
    …mount
    
    upstream commit: b363b33
    
    CIFS can allocate a few bytes to little for the nativeFileSystem field
    during tree connect response processing during mount.  This can result
    in a "Redzone overwritten" message to be logged.
    
    Signed-off-by: Sridhar Vinay <vinaysridhar@in.ibm.com>
    Acked-by: Shirish Pargaonkar <shirishp@us.ibm.com>
    CC: Stable <stable@kernel.org>
    Signed-off-by: Steve French <sfrench@us.ibm.com>
    [chrisw: minor backport to CHANGES file]
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  27. @bcopeland @chriswright

    ath5k: warn and correct rate for unknown hw rate indexes

    bcopeland authored chriswright committed
    upstream commit: b726604
    
    ath5k sets up a mapping table from the hardware rate index to
    the rate index used by mac80211; however, we have seen some
    received frames with incorrect rate indexes.  Such frames
    normally get dropped with a warning in __ieee80211_rx(),
    but it doesn't include enough information to track down the
    error.
    
    This patch adds a warning to hw_to_driver_rix for any lookups
    that result in a rate index of -1, then returns a valid rate so
    the frame can be processed.
    
    Changes-licensed-under: 3-Clause-BSD
    
    Signed-off-by: Bob Copeland <me@bobcopeland.com>
    Cc: stable@kernel.org
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    [chrisw: add db5b4f7 to backport]
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  28. @bcopeland @chriswright

    ath5k: disable MIB interrupts

    bcopeland authored chriswright committed
    upstream commit: 9ca9fb8
    
    The MIB interrupt fires whenever counters overflow; however without
    support for automatic noise immunity, we can sometimes get an interrupt
    storm.  The get_stats() callback reads the counters anyway so we can
    disable the interrupt for now until ANI is implemented.  This fixes
    the issue reported in http://bugzilla.kernel.org/show_bug.cgi?id=12647.
    
    Changes-licensed-under: 3-Clause-BSD
    
    Cc: stable@kernel.org
    Signed-off-by: Bob Copeland <me@bobcopeland.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  29. @chriswright

    b43: fix b43_plcp_get_bitrate_idx_ofdm return type

    Lorenzo Nava authored chriswright committed
    upstream commit: a3c0b87
    
    This patch fixes the return type of b43_plcp_get_bitrate_idx_ofdm. If
    the plcp contains an error, the function return value is 255 instead
    of -1, and the packet was not dropped. This causes a warning in
    __ieee80211_rx function because rate idx is out of range.
    
    Cc: stable@kernel.org
    Signed-off-by: Lorenzo Nava <navalorenx@gmail.com>
    Signed-off-by: Michael Buesch <mb@bu3sch.de>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  30. @chriswright

    ath9k: fix dma mapping leak of rx buffer upon rmmod

    Luis R. Rodriguez authored chriswright committed
    upstream commit: 051b919
    
    We were claiming DMA buffers on the RX tasklet but never
    upon a simple module removal.
    
    Cc: stable@kernel.org
    Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
    Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    [chrisw: backport to 2.6.29]
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  31. @bcopeland @chriswright

    ath5k: use spin_lock_irqsave for beacon lock

    bcopeland authored chriswright committed
    upstream commit: b5f0395
    
    ath5k_reset can be called from process context, which in turn can
    call ath5k_beacon_config which takes the sc->block spinlock.  Since
    it can also be taken in hard irq context, use spin_lock_irqsave
    everywhere.  This fixes a potential deadlock in adhoc mode.
    
    Changes-licensed-under: 3-Clause-BSD
    
    Cc: stable@kernel.org
    Signed-off-by: Bob Copeland <me@bobcopeland.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  32. @chriswright

    cifs: fix buffer format byte on NT Rename/hardlink

    Jeff Layton authored chriswright committed
    upstream commit: fcc7c09
    
    Discovered at Connnectathon 2009...
    
    The buffer format byte and the pad are transposed in NT_RENAME calls
    (which are used to set hardlinks). Most servers seem to ignore this
    fact, but NetApp filers throw back an error due to this problem. This
    patch fixes it.
    
    CC: Stable <stable@kernel.org>
    Signed-off-by: Jeff Layton <jlayton@redhat.com>
    Signed-off-by: Steve French <sfrench@us.ibm.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  33. @chriswright

    ath9k: downgrade xmit queue full message to xmit debug

    Luis R. Rodriguez authored chriswright committed
    upstream commit: c117fa0
    
    This is not a fatal message, hitting it simply means we're
    going to tell the upper layers to slow their horses down but
    as we make more descriptors available we let the show continue
    by waking up the queues in ath_wake_mac80211_queue().
    
    We downgrade this as otherwise we fill up your kernel log with
    messages which can be common under heavy traffic.
    
    Cc: stable@kernel.org
    Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
    Signed-off-by: John W. Linville <linville@tuxdriver.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  34. @aprzywar @chriswright

    KVM: SVM: set accessed bit for VMCB segment selectors

    aprzywar authored chriswright committed
    upstream commit: 1fbdc7a
    
    In the segment descriptor _cache_ the accessed bit is always set
    (although it can be cleared in the descriptor itself). Since Intel
    checks for this condition on a VMENTRY, set this bit in the AMD path
    to enable cross vendor migration.
    
    Cc: stable@kernel.org
    Signed-off-by: Andre Przywara <andre.przywara@amd.com>
    Acked-By: Amit Shah <amit.shah@redhat.com>
    Signed-off-by: Avi Kivity <avi@redhat.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
  35. @chriswright

    KVM: VMX: Don't allow uninhibited access to EFER on i386

    Avi Kivity authored chriswright committed
    upstream commit: 16175a7
    
    vmx_set_msr() does not allow i386 guests to touch EFER, but they can still
    do so through the default: label in the switch.  If they set EFER_LME, they
    can oops the host.
    
    Fix by having EFER access through the normal channel (which will check for
    EFER_LME) even on i386.
    
    Reported-and-tested-by: Benjamin Gilbert <bgilbert@cs.cmu.edu>
    Cc: stable@kernel.org
    Signed-off-by: Avi Kivity <avi@redhat.com>
    Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Something went wrong with that request. Please try again.