1. 03 Apr, 2015 6 commits
  2. 02 Apr, 2015 19 commits
  3. 01 Apr, 2015 15 commits
    • David S. Miller's avatar
      Merge tag 'wireless-drivers-for-davem-2015-04-01' of... · f5f321c4
      David S. Miller authored
      Merge tag 'wireless-drivers-for-davem-2015-04-01' of git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers
      
      Kalle Valo says:
      
      ====================
      iwlwifi:
      
      * fix a memory leak, we leaked memory each time the module
        was loaded.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      f5f321c4
    • David S. Miller's avatar
      Merge branch 'cxgb4-net' · 877e45d6
      David S. Miller authored
      Hariprasad Shenai says:
      
      ====================
      cxgb4 FW macro changes for new FW
      
      Fix to dump device log even in the case of firmware crash. Also
      incorporates changes for new FW.
      
      This patch series has been created against net tree and includes patches on
      cxgb4 driver.
      
      We have included all the maintainers of respective drivers. Kindly review the
      change and let us know in case of any review comments.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      877e45d6
    • Hariprasad Shenai's avatar
      cxgb4: Fix to dump devlog, even if FW is crashed · ae469b68
      Hariprasad Shenai authored
      Add new Common Code routines to retrieve Firmware Device Log
      parameters from PCIE_FW_PF[7]. The firmware initializes its Device Log very
      early on and stores the parameters for its location/size in that register.
      Using the parameters from the register allows us to access the Firmware
      Device Log even when the firmware crashes very early on or we're not
      attached to the firmware
      
      Based on original work by Casey Leedom <leedom@chelsio.com>
      Signed-off-by: default avatarHariprasad Shenai <hariprasad@chelsio.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      ae469b68
    • Hariprasad Shenai's avatar
      cxgb4: Firmware macro changes for fw verison 1.13.32.0 · 7ef65a42
      Hariprasad Shenai authored
      Adds new macro and few macro changes for fw version 1.13.32.0 also
      changes version string in driver to match 1.13.32.0
      Signed-off-by: default avatarHariprasad Shenai <hariprasad@chelsio.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      7ef65a42
    • David S. Miller's avatar
      Merge tag 'mac80211-for-davem-2015-04-01' of... · af3e09e6
      David S. Miller authored
      Merge tag 'mac80211-for-davem-2015-04-01' of git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211
      
      Johannes Berg says:
      
      ====================
      This contains just a single fix for a crash I happened to randomly
      run into today during testing. It's clearly been around for a while,
      but is pretty hard to trigger, even when I tried explicitly (and
      modified the code to make it more likely) it rarely did.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      af3e09e6
    • Linus Torvalds's avatar
      Merge tag 'iommu-fixes-v4.0-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu · d4039314
      Linus Torvalds authored
      Pull IOMMU fixes from Joerg Roedel:
       "This contains fixes for:
      
         - a VT-d issue where hardware domain-ids might be freed while still
           in use.
      
         - an ipmmu-vmsa issue where where the device-table was not zero
           terminated
      
         - unchecked register access issue in the arm-smmu driver"
      
      * tag 'iommu-fixes-v4.0-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu:
        iommu/vt-d: Remove unused variable
        iommu: ipmmu-vmsa: Add terminating entry for ipmmu_of_ids
        iommu/vt-d: Detach domain *only* from attached iommus
        iommu/arm-smmu: fix ARM_SMMU_FEAT_TRANS_OPS condition
      d4039314
    • Rusty Russell's avatar
      lguest: now needs PCI_DIRECT. · e1b7c029
      Rusty Russell authored
      Since commit 8e709469 ("lguest: add a dummy PCI host bridge.")
      lguest uses PCI, but it needs you to frob the ports directly.
      Signed-off-by: default avatarRusty Russell <rusty@rustcorp.com.au>
      Acked-by: default avatarIngo Molnar <mingo@kernel.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      e1b7c029
    • Linus Torvalds's avatar
      Merge tag 'lazytime_fix' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4 · b6c3a594
      Linus Torvalds authored
      Pull lazytime fixes from Ted Ts'o:
       "This fixes a problem in the lazy time patches, which can cause
        frequently updated inods to never have their timestamps updated.
      
        These changes guarantee that no timestamp on disk will be stale by
        more than 24 hours"
      
      * tag 'lazytime_fix' of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4:
        fs: add dirtytime_expire_seconds sysctl
        fs: make sure the timestamps for lazytime inodes eventually get written
      b6c3a594
    • Linus Torvalds's avatar
      Merge branch 'for-4.0' of git://linux-nfs.org/~bfields/linux · 1e848913
      Linus Torvalds authored
      Pull nfsd fixes from Bruce Fields:
       "Two main issues:
      
         - We found that turning on pNFS by default (when it's configured at
           build time) was too aggressive, so we want to switch the default
           before the 4.0 release.
      
         - Recent client changes to increase open parallelism uncovered a
           serious bug lurking in the server's open code.
      
        Also fix a krb5/selinux regression.
      
        The rest is mainly smaller pNFS fixes"
      
      * 'for-4.0' of git://linux-nfs.org/~bfields/linux:
        sunrpc: make debugfs file creation failure non-fatal
        nfsd: require an explicit option to enable pNFS
        NFSD: Fix bad update of layout in nfsd4_return_file_layout
        NFSD: Take care the return value from nfsd4_encode_stateid
        NFSD: Printk blocklayout length and offset as format 0x%llx
        nfsd: return correct lockowner when there is a race on hash insert
        nfsd: return correct openowner when there is a race to put one in the hash
        NFSD: Put exports after nfsd4_layout_verify fail
        NFSD: Error out when register_shrinker() fail
        NFSD: Take care the return value from nfsd4_decode_stateid
        NFSD: Check layout type when returning client layouts
        NFSD: restore trace event lost in mismerge
      1e848913
    • David S. Miller's avatar
      Merge branch 'bnx2' · 9c026424
      David S. Miller authored
      Yuval Mintz says:
      
      ====================
      bnx2x: kdump related fixes
      
      This patch series aims to fix bnx2x driver issues when loading in kdump kernel.
      Both issues fixed here would be fatal to the device, requiring full reset of
      the system in order to recover, preventing the device from serving its purpose
      in the kdump environment.
      ====================
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      9c026424
    • Yuval Mintz's avatar
      bnx2x: Fix kdump when iommu=on · da254fbc
      Yuval Mintz authored
      When IOMM-vtd is active, once main kernel crashes unfinished DMAE transactions
      will be blocked, putting the HW in an error state which will cause further
      transactions to timeout.
      
      Current employed logic uses wrong macros, causing the first function to be the
      only function that cleanups that error state during its probe/load.
      
      This patch allows all the functions to successfully re-load in kdump kernel.
      Signed-off-by: default avatarYuval Mintz <Yuval.Mintz@qlogic.com>
      Signed-off-by: default avatarAriel Elior <Ariel.Elior@qlogic.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      da254fbc
    • Yuval Mintz's avatar
      bnx2x: Fix kdump on 4-port device · 3d6b7253
      Yuval Mintz authored
      When running in a kdump kernel, it's very likely that due to sync. loss with
      management firmware the first PCI function to probe and reach the previous
      unload flow would decide it can reset the chip and continue onward. While doing
      so, it will only close its own Rx port.
      
      On a 4-port device where 2nd port on engine is a 1g-port, the 2nd port would
      allow ingress traffic after the chip is reset [assuming it was active on the
      first kernel]. This would later cause a HW attention.
      
      This changes driver flow to close both ports' 1g capabilities during the
      previous driver unload flow prior to the chip reset.
      Signed-off-by: default avatarYuval Mintz <Yuval.Mintz@qlogic.com>
      Signed-off-by: default avatarAriel Elior <Ariel.Elior@qlogic.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      3d6b7253
    • Johannes Berg's avatar
      mac80211: fix RX A-MPDU session reorder timer deletion · 788211d8
      Johannes Berg authored
      There's an issue with the way the RX A-MPDU reorder timer is
      deleted that can cause a kernel crash like this:
      
       * tid_rx is removed - call_rcu(ieee80211_free_tid_rx)
       * station is destroyed
       * reorder timer fires before ieee80211_free_tid_rx() runs,
         accessing the station, thus potentially crashing due to
         the use-after-free
      
      The station deletion is protected by synchronize_net(), but
      that isn't enough -- ieee80211_free_tid_rx() need not have
      run when that returns (it deletes the timer.) We could use
      rcu_barrier() instead of synchronize_net(), but that's much
      more expensive.
      
      Instead, to fix this, add a field tracking that the session
      is being deleted. In this case, the only re-arming of the
      timer happens with the reorder spinlock held, so make that
      code not rearm it if the session is being deleted and also
      delete the timer after setting that field. This ensures the
      timer cannot fire after ___ieee80211_stop_rx_ba_session()
      returns, which fixes the problem.
      
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarJohannes Berg <johannes.berg@intel.com>
      788211d8
    • Stefan Lippers-Hollmann's avatar
      x86/reboot: Add ASRock Q1900DC-ITX mainboard reboot quirk · 80313b30
      Stefan Lippers-Hollmann authored
      The ASRock Q1900DC-ITX mainboard (Baytrail-D) hangs randomly in
      both BIOS and UEFI mode while rebooting unless reboot=pci is
      used. Add a quirk to reboot via the pci method.
      
      The problem is very intermittent and hard to debug, it might succeed
      rebooting just fine 40 times in a row - but fails half a dozen times
      the next day. It seems to be slightly less common in BIOS CSM mode
      than native UEFI (with the CSM disabled), but it does happen in either
      mode. Since I've started testing this patch in late january, rebooting
      has been 100% reliable.
      
      Most of the time it already hangs during POST, but occasionally it
      might even make it through the bootloader and the kernel might even
      start booting, but then hangs before the mode switch. The same symptoms
      occur with grub-efi, gummiboot and grub-pc, just as well as (at least)
      kernel 3.16-3.19 and 4.0-rc6 (I haven't tried older kernels than 3.16).
      Upgrading to the most current mainboard firmware of the ASRock
      Q1900DC-ITX, version 1.20, does not improve the situation.
      
      ( Searching the web seems to suggest that other Bay Trail-D mainboards
        might be affected as well. )
      --
      Signed-off-by: default avatarStefan Lippers-Hollmann <s.l-h@gmx.de>
      Cc: <stable@vger.kernel.org>
      Cc: Matt Fleming <matt.fleming@intel.com>
      Link: http://lkml.kernel.org/r/20150330224427.0fb58e42@mirSigned-off-by: default avatarIngo Molnar <mingo@kernel.org>
      80313b30
    • Steve French's avatar
      Fix warning · 4c5930e8
      Steve French authored
      Coverity reports a warning due to unitialized attr structure in one
      code path.
      
      Reported by Coverity (CID 728535)
      Signed-off-by: default avatarSteve French <smfrench@gmail.com>
      Reviewed-by: default avatarJeff Layton <jlayton@samba.org>
      4c5930e8