1. 05 Jul, 2016 1 commit
  2. 21 Jun, 2016 4 commits
  3. 20 Jun, 2016 2 commits
  4. 14 Jun, 2016 3 commits
  5. 13 Jun, 2016 1 commit
    • Olof Johansson's avatar
      Merge tag 'renesas-arm64-dt-for-v4.8' of... · 045ab0c5
      Olof Johansson authored
      Merge tag 'renesas-arm64-dt-for-v4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas into next/dt64
      
      Renesas ARM64 Based SoC DT Updates for v4.8
      
      * Fix W=1 dtc warnings and other cleanups
      * Enable watchdog timer
      * Enable DMA for I2C
      * Increase the size of GIC-400 mapped registers: be nicer to hypervisors
      * Support RTS/CTS hardware flow control
      
      * tag 'renesas-arm64-dt-for-v4.8' of git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas:
        arm64: dts: r8a7795: Drop 0x from unit address of gic
        arm64: dts: salvator-x: Fix W=1 dtc warnings
        arm64: dts: r8a7795: Fix W=1 dtc warnings
        arm64: dts: r8a7795: Use SYSC "always-on" PM Domain for RWDT node
        arm64: dts: salvator-x: Enable watchdog timer
        arm64: dts: r8a7795: Add RWDT node
        arm64: dts: r8a7795: enable DMA for I2C
        arm64: dts: r8a7795: Increase the size of GIC-400 mapped registers
        arm64: dts: salvator-x: SCIF1 supports RTS/CTS hardware flow control
      Signed-off-by: default avatarOlof Johansson <olof@lixom.net>
      045ab0c5
  6. 03 Jun, 2016 1 commit
  7. 01 Jun, 2016 7 commits
  8. 31 May, 2016 6 commits
  9. 30 May, 2016 9 commits
  10. 29 May, 2016 3 commits
  11. 28 May, 2016 3 commits
    • Mikulas Patocka's avatar
      hpfs: implement the show_options method · 037369b8
      Mikulas Patocka authored
      The HPFS filesystem used generic_show_options to produce string that is
      displayed in /proc/mounts.  However, there is a problem that the options
      may disappear after remount.  If we mount the filesystem with option1
      and then remount it with option2, /proc/mounts should show both option1
      and option2, however it only shows option2 because the whole option
      string is replaced with replace_mount_options in hpfs_remount_fs.
      
      To fix this bug, implement the hpfs_show_options function that prints
      options that are currently selected.
      Signed-off-by: default avatarMikulas Patocka <mpatocka@redhat.com>
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      037369b8
    • Mikulas Patocka's avatar
      affs: fix remount failure when there are no options changed · 01d6e087
      Mikulas Patocka authored
      Commit c8f33d0b ("affs: kstrdup() memory handling") checks if the
      kstrdup function returns NULL due to out-of-memory condition.
      
      However, if we are remounting a filesystem with no change to
      filesystem-specific options, the parameter data is NULL.  In this case,
      kstrdup returns NULL (because it was passed NULL parameter), although no
      out of memory condition exists.  The mount syscall then fails with
      ENOMEM.
      
      This patch fixes the bug.  We fail with ENOMEM only if data is non-NULL.
      
      The patch also changes the call to replace_mount_options - if we didn't
      pass any filesystem-specific options, we don't call
      replace_mount_options (thus we don't erase existing reported options).
      
      Fixes: c8f33d0b ("affs: kstrdup() memory handling")
      Signed-off-by: default avatarMikulas Patocka <mpatocka@redhat.com>
      Cc: stable@vger.kernel.org	# v4.1+
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      01d6e087
    • Mikulas Patocka's avatar
      hpfs: fix remount failure when there are no options changed · 44d51706
      Mikulas Patocka authored
      Commit ce657611 ("hpfs: kstrdup() out of memory handling") checks if
      the kstrdup function returns NULL due to out-of-memory condition.
      
      However, if we are remounting a filesystem with no change to
      filesystem-specific options, the parameter data is NULL.  In this case,
      kstrdup returns NULL (because it was passed NULL parameter), although no
      out of memory condition exists.  The mount syscall then fails with
      ENOMEM.
      
      This patch fixes the bug.  We fail with ENOMEM only if data is non-NULL.
      
      The patch also changes the call to replace_mount_options - if we didn't
      pass any filesystem-specific options, we don't call
      replace_mount_options (thus we don't erase existing reported options).
      
      Fixes: ce657611 ("hpfs: kstrdup() out of memory handling")
      Signed-off-by: default avatarMikulas Patocka <mpatocka@redhat.com>
      Cc: stable@vger.kernel.org
      Signed-off-by: default avatarLinus Torvalds <torvalds@linux-foundation.org>
      44d51706