1. 03 11月, 2017 1 次提交
  2. 23 10月, 2017 1 次提交
  3. 21 10月, 2017 2 次提交
  4. 20 10月, 2017 1 次提交
  5. 19 10月, 2017 5 次提交
  6. 16 10月, 2017 1 次提交
  7. 14 10月, 2017 1 次提交
  8. 08 10月, 2017 1 次提交
  9. 06 10月, 2017 1 次提交
    • J
      dm raid: fix incorrect status output at the end of a "recover" process · 41dcf197
      Jonathan Brassow 提交于
      There are three important fields that indicate the overall health and
      status of an array: dev_health, sync_ratio, and sync_action.  They tell
      us the condition of the devices in the array, and the degree to which
      the array is synchronized.
      
      This commit fixes a condition that is reported incorrectly.  When a member
      of the array is being rebuilt or a new device is added, the "recover"
      process is used to synchronize it with the rest of the array.  When the
      process is complete, but the sync thread hasn't yet been reaped, it is
      possible for the state of MD to be:
       mddev->recovery = [ MD_RECOVERY_RUNNING MD_RECOVERY_RECOVER MD_RECOVERY_DONE ]
       curr_resync_completed = <max dev size> (but not MaxSector)
       and all rdevs to be In_sync.
      This causes the 'array_in_sync' output parameter that is passed to
      rs_get_progress() to be computed incorrectly and reported as 'false' --
      or not in-sync.  This in turn causes the dev_health status characters to
      be reported as all 'a', rather than the proper 'A'.
      
      This can cause erroneous output for several seconds at a time when tools
      will want to be checking the condition due to events that are raised at
      the end of a sync process.  Fix this by properly calculating the
      'array_in_sync' return parameter in rs_get_progress().
      
      Also, remove an unnecessary intermediate 'recovery_cp' variable in
      rs_get_progress().
      Signed-off-by: NJonathan Brassow <jbrassow@redhat.com>
      Signed-off-by: NMike Snitzer <snitzer@redhat.com>
      41dcf197
  10. 05 10月, 2017 3 次提交
  11. 04 10月, 2017 2 次提交
  12. 02 10月, 2017 1 次提交
  13. 28 9月, 2017 1 次提交
  14. 24 9月, 2017 2 次提交
  15. 22 9月, 2017 1 次提交
  16. 20 9月, 2017 3 次提交
    • M
      ipv6: fix net.ipv6.conf.all interface DAD handlers · 35e015e1
      Matteo Croce 提交于
      Currently, writing into
      net.ipv6.conf.all.{accept_dad,use_optimistic,optimistic_dad} has no effect.
      Fix handling of these flags by:
      
      - using the maximum of global and per-interface values for the
        accept_dad flag. That is, if at least one of the two values is
        non-zero, enable DAD on the interface. If at least one value is
        set to 2, enable DAD and disable IPv6 operation on the interface if
        MAC-based link-local address was found
      
      - using the logical OR of global and per-interface values for the
        optimistic_dad flag. If at least one of them is set to one, optimistic
        duplicate address detection (RFC 4429) is enabled on the interface
      
      - using the logical OR of global and per-interface values for the
        use_optimistic flag. If at least one of them is set to one,
        optimistic addresses won't be marked as deprecated during source address
        selection on the interface.
      
      While at it, as we're modifying the prototype for ipv6_use_optimistic_addr(),
      drop inline, and let the compiler decide.
      
      Fixes: 7fd2561e ("net: ipv6: Add a sysctl to make optimistic addresses useful candidates")
      Signed-off-by: NMatteo Croce <mcroce@redhat.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      35e015e1
    • R
      PM: docs: Drop an excess character from devices.rst · b247c211
      Rafael J. Wysocki 提交于
      Drop an excess "`" from Documentation/driver-api/pm/devices.rst.
      
      Fixes: 2728b2d2 (PM / core / docs: Convert sleep states API document to reST)
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      b247c211
    • A
      dt-bindings: fix vendor prefix for Abracon · a6899e90
      Alexandre Belloni 提交于
      Commit 446810f2 ("of: add vendor prefix for Abracon Corporation")
      claimed that "abcn" was used as the vendor prefix while in fact "abracon"
      was used in the subsequent commits. It is also the only prefix used in the
      tree.
      Signed-off-by: NAlexandre Belloni <alexandre.belloni@free-electrons.com>
      [robh: fix alphabetical order]
      Signed-off-by: NRob Herring <robh@kernel.org>
      a6899e90
  17. 19 9月, 2017 4 次提交
  18. 18 9月, 2017 2 次提交
  19. 17 9月, 2017 2 次提交
  20. 15 9月, 2017 1 次提交
  21. 14 9月, 2017 2 次提交
  22. 11 9月, 2017 1 次提交
  23. 10 9月, 2017 1 次提交