1. 14 3月, 2009 2 次提交
  2. 06 2月, 2009 1 次提交
    • P
      netlink: change return-value logic of netlink_broadcast() · ff491a73
      Pablo Neira Ayuso 提交于
      Currently, netlink_broadcast() reports errors to the caller if no
      messages at all were delivered:
      
      1) If, at least, one message has been delivered correctly, returns 0.
      2) Otherwise, if no messages at all were delivered due to skb_clone()
         failure, return -ENOBUFS.
      3) Otherwise, if there are no listeners, return -ESRCH.
      
      With this patch, the caller knows if the delivery of any of the
      messages to the listeners have failed:
      
      1) If it fails to deliver any message (for whatever reason), return
         -ENOBUFS.
      2) Otherwise, if all messages were delivered OK, returns 0.
      3) Otherwise, if no listeners, return -ESRCH.
      
      In the current ctnetlink code and in Netfilter in general, we can add
      reliable logging and connection tracking event delivery by dropping the
      packets whose events were not successfully delivered over Netlink. Of
      course, this option would be settable via /proc as this approach reduces
      performance (in terms of filtered connections per seconds by a stateful
      firewall) but providing reliable logging and event delivery (for
      conntrackd) in return.
      
      This patch also changes some clients of netlink_broadcast() that
      may report ENOBUFS errors via printk. This error handling is not
      of any help. Instead, the userspace daemons that are listening to
      those netlink messages should resync themselves with the kernel-side
      if they hit ENOBUFS.
      
      BTW, netlink_broadcast() clients include those that call
      cn_netlink_send(), nlmsg_multicast() and genlmsg_multicast() since they
      internally call netlink_broadcast() and return its error value.
      Signed-off-by: NPablo Neira Ayuso <pablo@netfilter.org>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      ff491a73
  3. 03 1月, 2009 1 次提交
  4. 13 10月, 2008 3 次提交
  5. 04 10月, 2008 1 次提交
    • J
      [SCSI] scsi_host_lookup: error returns and NULL pointers · 315cb0ad
      James Smart 提交于
      This patch cleans up the behavior of scsi_host_lookup().
      
      The original implementation attempted to use the dual role of
      either returning a pointer value, or a negative error code.
      User's needed to use IS_ERR() to check the result. Additionally,
      the IS_ERR() macro never checks for when a NULL pointer was
      returned, so a NULL pointer actually passes with a success case.
      Note: scsi_host_get(), used by scsi_host_lookup(), can return
      a NULL pointer.
      
      Talk about a mudhole for the unitiated to step into....
      
      This patch converts scsi_host_lookup() to return either NULL
      or a valid pointer. The consumers were updated for the change.
      Signed-off-by: NJames Smart <james.smart@emulex.com>
      Signed-off-by: NJames Bottomley <James.Bottomley@HansenPartnership.com>
      315cb0ad
  6. 22 7月, 2008 2 次提交
  7. 12 7月, 2008 12 次提交
  8. 20 4月, 2008 1 次提交
  9. 06 3月, 2008 1 次提交
  10. 28 2月, 2008 1 次提交
  11. 22 2月, 2008 1 次提交
  12. 08 2月, 2008 6 次提交
  13. 29 1月, 2008 1 次提交
  14. 12 1月, 2008 7 次提交