1. 16 11月, 2019 7 次提交
  2. 07 11月, 2019 1 次提交
  3. 30 10月, 2019 1 次提交
  4. 26 10月, 2019 2 次提交
  5. 25 10月, 2019 1 次提交
    • T
      net: remove unnecessary variables and callback · f3b0a18b
      Taehee Yoo 提交于
      This patch removes variables and callback these are related to the nested
      device structure.
      devices that can be nested have their own nest_level variable that
      represents the depth of nested devices.
      In the previous patch, new {lower/upper}_level variables are added and
      they replace old private nest_level variable.
      So, this patch removes all 'nest_level' variables.
      
      In order to avoid lockdep warning, ->ndo_get_lock_subclass() was added
      to get lockdep subclass value, which is actually lower nested depth value.
      But now, they use the dynamic lockdep key to avoid lockdep warning instead
      of the subclass.
      So, this patch removes ->ndo_get_lock_subclass() callback.
      Signed-off-by: NTaehee Yoo <ap420073@gmail.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      f3b0a18b
  6. 23 10月, 2019 8 次提交
  7. 11 10月, 2019 3 次提交
  8. 10 10月, 2019 5 次提交
  9. 21 8月, 2019 1 次提交
    • J
      net/smc: make sure EPOLLOUT is raised · 4651d180
      Jason Baron 提交于
      Currently, we are only explicitly setting SOCK_NOSPACE on a write timeout
      for non-blocking sockets. Epoll() edge-trigger mode relies on SOCK_NOSPACE
      being set when -EAGAIN is returned to ensure that EPOLLOUT is raised.
      Expand the setting of SOCK_NOSPACE to non-blocking sockets as well that can
      use SO_SNDTIMEO to adjust their write timeout. This mirrors the behavior
      that Eric Dumazet introduced for tcp sockets.
      Signed-off-by: NJason Baron <jbaron@akamai.com>
      Cc: Eric Dumazet <edumazet@google.com>
      Cc: Ursula Braun <ubraun@linux.ibm.com>
      Cc: Karsten Graul <kgraul@linux.ibm.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4651d180
  10. 06 8月, 2019 2 次提交
  11. 28 6月, 2019 1 次提交
  12. 27 6月, 2019 2 次提交
  13. 03 6月, 2019 1 次提交
  14. 21 5月, 2019 2 次提交
  15. 03 5月, 2019 1 次提交
  16. 28 4月, 2019 1 次提交
    • J
      genetlink: optionally validate strictly/dumps · ef6243ac
      Johannes Berg 提交于
      Add options to strictly validate messages and dump messages,
      sometimes perhaps validating dump messages non-strictly may
      be required, so add an option for that as well.
      
      Since none of this can really be applied to existing commands,
      set the options everwhere using the following spatch:
      
          @@
          identifier ops;
          expression X;
          @@
          struct genl_ops ops[] = {
          ...,
           {
                  .cmd = X,
          +       .validate = GENL_DONT_VALIDATE_STRICT | GENL_DONT_VALIDATE_DUMP,
                  ...
           },
          ...
          };
      
      For new commands one should just not copy the .validate 'opt-out'
      flags and thus get strict validation.
      Signed-off-by: NJohannes Berg <johannes.berg@intel.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ef6243ac
  17. 13 4月, 2019 1 次提交