1. 06 Feb, 2014 1 commit
  2. 05 Feb, 2014 5 commits
    • Linus Torvalds's avatar
      Merge git://git.infradead.org/users/willy/linux-nvme · 8352650a
      Linus Torvalds authored
      Pull NVMe driver update from Matthew Wilcox:
       "Looks like I missed the merge window ...  but these are almost all
        bugfixes anyway (the ones that aren't have been baking for months)"
      
      * git://git.infradead.org/users/willy/linux-nvme:
        NVMe: Namespace use after free on surprise removal
        NVMe: Correct uses of INIT_WORK
        NVMe: Include device and queue numbers in interrupt name
        NVMe: Add a pci_driver shutdown method
        NVMe: Disable admin queue on init failure
        NVMe: Dynamically allocate partition numbers
        NVMe: Async IO queue deletion
        NVMe: Surprise removal handling
        NVMe: Abort timed out commands
        NVMe: Schedule reset for failed controllers
        NVMe: Device resume error handling
        NVMe: Cache dev->pci_dev in a local pointer
        NVMe: Fix lockdep warnings
        NVMe: compat SG_IO ioctl
        NVMe: remove deprecated IRQF_DISABLED
        NVMe: Avoid shift operation when writing cq head doorbell
      8352650a
    • Linus Torvalds's avatar
      Merge tag 'regulator-v3.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator · 71c27a8c
      Linus Torvalds authored
      Pull regulator fixes from Mark Brown:
       "A couple of driver fixes here but the main thing is a fix to the
        checks for deferred probe non-DT systems with fully specified
        regulators which had been broken by a device tree fix which meant that
        we wouldn't insert optional regulators.
      
        This had slipped through the cracks since very few systems do that in
        the first place and those that do it in mainline don't need optional
        regulators anyway"
      
      * tag 'regulator-v3.14-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator:
        regulator: s2mps11: Fix NULL pointer of_node value when using platform data
        regulator: core: Correct default return value for full constraints
        regulator: ab3100: cast fix
      71c27a8c
    • Linus Torvalds's avatar
      Merge git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 · 4293242d
      Linus Torvalds authored
      Pull crypto fixes from Herbert Xu:
       "This fixes a number of concurrency issues on s390 where multiple users
        of the same crypto transform may clobber each other's results"
      
      * git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6:
        crypto: s390 - fix des and des3_ede ctr concurrency issue
        crypto: s390 - fix des and des3_ede cbc concurrency issue
        crypto: s390 - fix concurrency issue in aes-ctr mode
      4293242d
    • Ingo Molnar's avatar
      x86: Disable CONFIG_X86_DECODER_SELFTEST in allmod/allyesconfigs · f8f20234
      Ingo Molnar authored
      It can take some time to validate the image, make sure
      {allyes|allmod}config doesn't enable it.
      
      I'd say randconfig will cover it often enough, and the failure is also
      borderline build coverage related: you cannot really make the decoder
      test fail via source level changes, only with changes in the build
      environment, so I agree with Andi that we can disable this one too.
      Signed-off-by: default avatarIngo Molnar <mingo@kernel.org>
      Acked-by: Paul Gortmaker paul.gortmaker@windriver.com>
      Suggested-and-acked-by: Andi Kleen andi@firstfloor.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      f8f20234
    • Linus Torvalds's avatar
      execve: use 'struct filename *' for executable name passing · c4ad8f98
      Linus Torvalds authored
      This changes 'do_execve()' to get the executable name as a 'struct
      filename', and to free it when it is done.  This is what the normal
      users want, and it simplifies and streamlines their error handling.
      
      The controlled lifetime of the executable name also fixes a
      use-after-free problem with the trace_sched_process_exec tracepoint: the
      lifetime of the passed-in string for kernel users was not at all
      obvious, and the user-mode helper code used UMH_WAIT_EXEC to serialize
      the pathname allocation lifetime with the execve() having finished,
      which in turn meant that the trace point that happened after
      mm_release() of the old process VM ended up using already free'd memory.
      
      To solve the kernel string lifetime issue, this simply introduces
      "getname_kernel()" that works like the normal user-space getname()
      function, except with the source coming from kernel memory.
      
      As Oleg points out, this also means that we could drop the tcomm[] array
      from 'struct linux_binprm', since the pathname lifetime now covers
      setup_new_exec().  That would be a separate cleanup.
      Reported-by: default avatarIgor Zhbanov <i.zhbanov@samsung.com>
      Tested-by: default avatarSteven Rostedt <rostedt@goodmis.org>
      Cc: Oleg Nesterov <oleg@redhat.com>
      Cc: Al Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      c4ad8f98
  3. 04 Feb, 2014 5 commits
  4. 03 Feb, 2014 11 commits
  5. 02 Feb, 2014 13 commits
  6. 01 Feb, 2014 5 commits