1. 08 8月, 2015 1 次提交
  2. 04 7月, 2015 1 次提交
  3. 01 6月, 2015 1 次提交
    • S
      net/rds: Add setsockopt support for SO_RDS_TRANSPORT · d97dac54
      Sowmini Varadhan 提交于
      An application may deterministically attach the underlying transport for
      a PF_RDS socket by invoking setsockopt(2) with the SO_RDS_TRANSPORT
      option at the SOL_RDS level. The integer argument to setsockopt must be
      one of the RDS_TRANS_* transport types, e.g., RDS_TRANS_TCP. The option
      must be specified before invoking bind(2) on the socket, and may only
      be used once on the socket. An attempt to set the option on a bound
      socket, or to invoke the option after a successful SO_RDS_TRANSPORT
      attachment, will return EOPNOTSUPP.
      Signed-off-by: NSowmini Varadhan <sowmini.varadhan@oracle.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      d97dac54
  4. 09 9月, 2010 1 次提交
    • Z
      RDS: have sockets get transport module references · 5adb5bc6
      Zach Brown 提交于
      Right now there's nothing to stop the various paths that use
      rs->rs_transport from racing with rmmod and executing freed transport
      code.  The simple fix is to have binding to a transport also hold a
      reference to the transport's module, removing this class of races.
      
      We already had an unused t_owner field which was set for the modular
      transports and which wasn't set for the built-in loop transport.
      Signed-off-by: NZach Brown <zach.brown@oracle.com>
      5adb5bc6
  5. 24 8月, 2009 2 次提交
  6. 27 2月, 2009 1 次提交