1. 16 2月, 2010 2 次提交
  2. 29 11月, 2009 2 次提交
  3. 26 11月, 2009 1 次提交
  4. 19 11月, 2009 1 次提交
  5. 07 11月, 2009 1 次提交
    • A
      net/x25: push BKL usage into x25_proto · 91774904
      Arnd Bergmann 提交于
      The x25 driver uses lock_kernel() implicitly through
      its proto_ops wrapper. The makes the usage explicit
      in order to get rid of that wrapper and to better document
      the usage of the BKL.
      
      The next step should be to get rid of the usage of the BKL
      in x25 entirely, which requires understanding what data
      structures need serialized accesses.
      
      Cc: Henner Eisen <eis@baty.hanse.de>
      Cc: David S. Miller <davem@davemloft.net>
      Cc: linux-x25@vger.kernel.org
      Cc: netdev@vger.kernel.org
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      91774904
  6. 06 11月, 2009 1 次提交
  7. 13 10月, 2009 1 次提交
  8. 07 10月, 2009 1 次提交
  9. 01 10月, 2009 1 次提交
  10. 13 7月, 2009 1 次提交
  11. 18 6月, 2009 1 次提交
  12. 17 6月, 2009 1 次提交
  13. 16 6月, 2009 1 次提交
  14. 27 3月, 2009 1 次提交
  15. 14 3月, 2009 1 次提交
  16. 10 3月, 2009 1 次提交
  17. 01 2月, 2009 1 次提交
  18. 20 7月, 2008 1 次提交
  19. 17 6月, 2008 2 次提交
  20. 26 3月, 2008 2 次提交
  21. 01 2月, 2008 1 次提交
  22. 29 1月, 2008 1 次提交
    • E
      [X25]: Avoid divides and sparse warnings · 6bf1574e
      Eric Dumazet 提交于
         CHECK   net/x25/af_x25.c
      net/x25/af_x25.c:117:46: warning: expensive signed divide
         CHECK   net/x25/x25_facilities.c
      net/x25/x25_facilities.c:209:30: warning: expensive signed divide
         CHECK   net/x25/x25_in.c
      net/x25/x25_in.c:250:26: warning: expensive signed divide
         CHECK   net/x25/x25_proc.c
      net/x25/x25_proc.c:48:11: warning: context imbalance in 'x25_seq_route_start'
      - wrong count at exit
      net/x25/x25_proc.c:72:13: warning: context imbalance in 'x25_seq_route_stop' -
      unexpected unlock
      net/x25/x25_proc.c:112:11: warning: context imbalance in
      'x25_seq_socket_start' - wrong count at exit
      net/x25/x25_proc.c:129:13: warning: context imbalance in 'x25_seq_socket_stop'
      - unexpected unlock
      net/x25/x25_proc.c:190:11: warning: context imbalance in
      'x25_seq_forward_start' - wrong count at exit
      net/x25/x25_proc.c:215:13: warning: context imbalance in
      'x25_seq_forward_stop' - unexpected unlock
         CHECK   net/x25/x25_subr.c
      net/x25/x25_subr.c:362:57: warning: expensive signed divide
      Signed-off-by: NEric Dumazet <dada1@cosmosbay.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      6bf1574e
  23. 01 11月, 2007 1 次提交
  24. 11 10月, 2007 2 次提交
    • E
      [NET]: Make device event notification network namespace safe · e9dc8653
      Eric W. Biederman 提交于
      Every user of the network device notifiers is either a protocol
      stack or a pseudo device.  If a protocol stack that does not have
      support for multiple network namespaces receives an event for a
      device that is not in the initial network namespace it quite possibly
      can get confused and do the wrong thing.
      
      To avoid problems until all of the protocol stacks are converted
      this patch modifies all netdev event handlers to ignore events on
      devices that are not in the initial network namespace.
      
      As the rest of the code is made network namespace aware these
      checks can be removed.
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      e9dc8653
    • E
      [NET]: Make socket creation namespace safe. · 1b8d7ae4
      Eric W. Biederman 提交于
      This patch passes in the namespace a new socket should be created in
      and has the socket code do the appropriate reference counting.  By
      virtue of this all socket create methods are touched.  In addition
      the socket create methods are modified so that they will fail if
      you attempt to create a socket in a non-default network namespace.
      
      Failing if we attempt to create a socket outside of the default
      network namespace ensures that as we incrementally make the network stack
      network namespace aware we will not export functionality that someone
      has not audited and made certain is network namespace safe.
      Allowing us to partially enable network namespaces before all of the
      exotic protocols are supported.
      
      Any protocol layers I have missed will fail to compile because I now
      pass an extra parameter into the socket creation code.
      
      [ Integrated AF_IUCV build fixes from Andrew Morton... -DaveM ]
      Signed-off-by: NEric W. Biederman <ebiederm@xmission.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      1b8d7ae4
  25. 09 5月, 2007 1 次提交
  26. 26 4月, 2007 4 次提交
  27. 11 2月, 2007 1 次提交
  28. 09 2月, 2007 2 次提交
  29. 04 1月, 2007 1 次提交
  30. 01 7月, 2006 1 次提交
  31. 22 3月, 2006 1 次提交