1. 26 3月, 2006 1 次提交
    • D
      [PATCH] POLLRDHUP/EPOLLRDHUP handling for half-closed devices notifications · f348d70a
      Davide Libenzi 提交于
      Implement the half-closed devices notifiation, by adding a new POLLRDHUP
      (and its alias EPOLLRDHUP) bit to the existing poll/select sets.  Since the
      existing POLLHUP handling, that does not report correctly half-closed
      devices, was feared to be changed, this implementation leaves the current
      POLLHUP reporting unchanged and simply add a new bit that is set in the few
      places where it makes sense.  The same thing was discussed and conceptually
      agreed quite some time ago:
      
      http://lkml.org/lkml/2003/7/12/116
      
      Since this new event bit is added to the existing Linux poll infrastruture,
      even the existing poll/select system calls will be able to use it.  As far
      as the existing POLLHUP handling, the patch leaves it as is.  The
      pollrdhup-2.6.16.rc5-0.10.diff defines the POLLRDHUP for all the existing
      archs and sets the bit in the six relevant files.  The other attached diff
      is the simple change required to sys/epoll.h to add the EPOLLRDHUP
      definition.
      
      There is "a stupid program" to test POLLRDHUP delivery here:
      
       http://www.xmailserver.org/pollrdhup-test.c
      
      It tests poll(2), but since the delivery is same epoll(2) will work equally.
      Signed-off-by: NDavide Libenzi <davidel@xmailserver.org>
      Cc: "David S. Miller" <davem@davemloft.net>
      Cc: Michael Kerrisk <mtk-manpages@gmx.net>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      f348d70a
  2. 21 3月, 2006 17 次提交
  3. 04 1月, 2006 6 次提交
  4. 21 11月, 2005 1 次提交
  5. 09 11月, 2005 1 次提交
  6. 21 10月, 2005 1 次提交
    • H
      [DCCP]: Make dccp_write_xmit always free the packet · ffa29347
      Herbert Xu 提交于
      icmp_send doesn't use skb->sk at all so even if skb->sk has already
      been freed it can't cause crash there (it would've crashed somewhere
      else first, e.g., ip_queue_xmit).
      
      I found a double-free on an skb that could explain this though.
      dccp_sendmsg and dccp_write_xmit are a little confused as to what
      should free the packet when something goes wrong.  Sometimes they
      both go for the ball and end up in each other's way.
      
      This patch makes dccp_write_xmit always free the packet no matter
      what.  This makes sense since dccp_transmit_skb which in turn comes
      from the fact that ip_queue_xmit always frees the packet.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NArnaldo Carvalho de Melo <acme@mandriva.com>
      ffa29347
  7. 18 9月, 2005 1 次提交
  8. 17 9月, 2005 1 次提交
  9. 30 8月, 2005 11 次提交