1. 24 3月, 2020 2 次提交
  2. 04 3月, 2020 3 次提交
  3. 29 2月, 2020 1 次提交
  4. 27 2月, 2020 1 次提交
  5. 26 2月, 2020 2 次提交
  6. 25 2月, 2020 1 次提交
  7. 24 2月, 2020 1 次提交
  8. 19 2月, 2020 1 次提交
  9. 05 2月, 2020 1 次提交
    • J
      devlink: report 0 after hitting end in region read · d5b90e99
      Jacob Keller 提交于
      commit fdd41ec2 ("devlink: Return right error code in case of errors
      for region read") modified the region read code to report errors
      properly in unexpected cases.
      
      In the case where the start_offset and ret_offset match, it unilaterally
      converted this into an error. This causes an issue for the "dump"
      version of the command. In this case, the devlink region dump will
      always report an invalid argument:
      
      000000000000ffd0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
      000000000000ffe0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
      devlink answers: Invalid argument
      000000000000fff0 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
      
      This occurs because the expected flow for the dump is to return 0 after
      there is no further data.
      
      The simplest fix would be to stop converting the error code to -EINVAL
      if start_offset == ret_offset. However, avoid unnecessary work by
      checking for when start_offset is larger than the region size and
      returning 0 upfront.
      
      Fixes: fdd41ec2 ("devlink: Return right error code in case of errors for region read")
      Signed-off-by: NJacob Keller <jacob.e.keller@intel.com>
      Acked-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d5b90e99
  10. 25 1月, 2020 1 次提交
  11. 19 1月, 2020 3 次提交
  12. 12 1月, 2020 1 次提交
  13. 11 1月, 2020 1 次提交
    • I
      devlink: Wait longer before warning about unset port type · 4c582234
      Ido Schimmel 提交于
      The commit cited below causes devlink to emit a warning if a type was
      not set on a devlink port for longer than 30 seconds to "prevent
      misbehavior of drivers". This proved to be problematic when
      unregistering the backing netdev. The flow is always:
      
      devlink_port_type_clear()	// schedules the warning
      unregister_netdev()		// blocking
      devlink_port_unregister()	// cancels the warning
      
      The call to unregister_netdev() can block for long periods of time for
      various reasons: RTNL lock is contended, large amounts of configuration
      to unroll following dismantle of the netdev, etc. This results in
      devlink emitting a warning despite the driver behaving correctly.
      
      In emulated environments (of future hardware) which are usually very
      slow, the warning can also be emitted during port creation as more than
      30 seconds can pass between the time the devlink port is registered and
      when its type is set.
      
      In addition, syzbot has hit this warning [1] 1974 times since 07/11/19
      without being able to produce a reproducer. Probably because
      reproduction depends on the load or other bugs (e.g., RTNL not being
      released).
      
      To prevent bogus warnings, increase the timeout to 1 hour.
      
      [1] https://syzkaller.appspot.com/bug?id=e99b59e9c024a666c9f7450dc162a4b74d09d9cb
      
      Fixes: 136bf27f ("devlink: add warning in case driver does not set port type")
      Signed-off-by: NIdo Schimmel <idosch@mellanox.com>
      Reported-by: syzbot+b0a18ed7b08b735d2f41@syzkaller.appspotmail.com
      Reported-by: NAlex Veber <alexve@mellanox.com>
      Tested-by: NAlex Veber <alexve@mellanox.com>
      Acked-by: NJiri Pirko <jiri@mellanox.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4c582234
  14. 09 1月, 2020 2 次提交
  15. 13 11月, 2019 1 次提交
  16. 12 11月, 2019 2 次提交
  17. 10 11月, 2019 1 次提交
  18. 09 11月, 2019 1 次提交
  19. 08 11月, 2019 2 次提交
  20. 12 10月, 2019 2 次提交
  21. 07 10月, 2019 1 次提交
  22. 06 10月, 2019 2 次提交
  23. 05 10月, 2019 3 次提交
  24. 02 10月, 2019 1 次提交
  25. 14 9月, 2019 2 次提交
  26. 11 9月, 2019 1 次提交