1. 29 11月, 2009 2 次提交
  2. 26 11月, 2009 1 次提交
  3. 19 11月, 2009 1 次提交
  4. 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
  5. 06 11月, 2009 1 次提交
  6. 13 10月, 2009 1 次提交
  7. 07 10月, 2009 1 次提交
  8. 01 10月, 2009 1 次提交
  9. 13 7月, 2009 1 次提交
  10. 18 6月, 2009 1 次提交
  11. 17 6月, 2009 1 次提交
  12. 16 6月, 2009 1 次提交
  13. 27 3月, 2009 1 次提交
  14. 14 3月, 2009 1 次提交
  15. 10 3月, 2009 1 次提交
  16. 01 2月, 2009 1 次提交
  17. 20 7月, 2008 1 次提交
  18. 17 6月, 2008 2 次提交
  19. 26 3月, 2008 2 次提交
  20. 01 2月, 2008 1 次提交
  21. 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
  22. 01 11月, 2007 1 次提交
  23. 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
  24. 09 5月, 2007 1 次提交
  25. 26 4月, 2007 4 次提交
  26. 11 2月, 2007 1 次提交
  27. 09 2月, 2007 2 次提交
  28. 04 1月, 2007 1 次提交
  29. 01 7月, 2006 1 次提交
  30. 22 3月, 2006 3 次提交
    • S
      [X25]: dte facilities 32 64 ioctl conversion · 9a6b9f2e
      Shaun Pereira 提交于
      Allows dte facility patch to use 32 64 bit ioctl conversion mechanism
      Signed-off-by: NShaun Pereira <spereira@tusc.com.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      9a6b9f2e
    • S
      [X25]: allow ITU-T DTE facilities for x25 · a64b7b93
      Shaun Pereira 提交于
      Allows use of the optional user facility to insert ITU-T
      (http://www.itu.int/ITU-T/) specified DTE facilities in call set-up x25
      packets.  This feature is optional; no facilities will be added if the ioctl
      is not used, and call setup packet remains the same as before.
      
      If the ioctls provided by the patch are used, then a facility marker will be
      added to the x25 packet header so that the called dte address extension
      facility can be differentiated from other types of facilities (as described in
      the ITU-T X.25 recommendation) that are also allowed in the x25 packet header.
      
      Facility markers are made up of two octets, and may be present in the x25
      packet headers of call-request, incoming call, call accepted, clear request,
      and clear indication packets.  The first of the two octets represents the
      facility code field and is set to zero by this patch.  The second octet of the
      marker represents the facility parameter field and is set to 0x0F because the
      marker will be inserted before ITU-T type DTE facilities.
      
      Since according to ITU-T X.25 Recommendation X.25(10/96)- 7.1 "All networks
      will support the facility markers with a facility parameter field set to all
      ones or to 00001111", therefore this patch should work with all x.25 networks.
      
      While there are many ITU-T DTE facilities, this patch implements only the
      called and calling address extension, with placeholders in the
      x25_dte_facilities structure for the rest of the facilities.
      
      Testing:
      
      This patch was tested using a cisco xot router connected on its serial ports
      to an X.25 network, and on its lan ports to a host running an xotd daemon.
      
      It is also possible to test this patch using an xotd daemon and an x25tap
      patch, where the xotd daemons work back-to-back without actually using an x.25
      network.  See www.fyonne.net for details on how to do this.
      Signed-off-by: NShaun Pereira <spereira@tusc.com.au>
      Acked-by: NAndrew Hendry <ahendry@tusc.com.au>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      a64b7b93
    • S
      [X25]: fix kernel error message 64 bit kernel · bac37ec8
      Shaun Pereira 提交于
      Fixes the following error from kernel
      T2 kernel: schedule_timeout:
      wrong timeout value ffffffffffffffff from ffffffff88164796
      Signed-off-by: NShaun Pereira <spereira@tusc.com.au>
      Acked-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      bac37ec8