1. 17 3月, 2010 1 次提交
  2. 27 2月, 2010 1 次提交
    • A
      dvb-core: Fix DoS bug in ULE decapsulation code that can be triggered by an invalid Payload Pointer · 29e1fa35
      Ang Way Chuang 提交于
      ULE (Unidirectional Lightweight Encapsulation RFC 4326) decapsulation
      has a bug that causes endless loop when Payload Pointer of MPEG2-TS
      frame is 182 or 183.  Anyone who sends malicious MPEG2-TS frame will
      cause the receiver of ULE SNDU to go into endless loop.
      
      This patch was generated and tested against linux-2.6.32.9 and should
      apply cleanly to linux-2.6.33 as well because there was only one typo
      fix to dvb_net.c since v2.6.32.
      
      This bug was brought to you by modern day Santa Claus who decided to
      shower the satellite dish at Keio University with heavy snow causing
      huge burst of errors.  We, receiver end, received Santa Claus's gift in
      the form of kernel bug.
      
      Care has been taken not to introduce more bug by fixing this bug, but
      please scrutinize the code for I always produces buggy code.
      Signed-off-by: NAng Way Chuang <wcang79@gmail.com>
      Acked-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      Cc: stable@kernel.org
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      29e1fa35
  3. 13 2月, 2010 1 次提交
  4. 07 1月, 2010 1 次提交
  5. 09 11月, 2009 1 次提交
  6. 12 10月, 2009 1 次提交
  7. 06 7月, 2009 1 次提交
  8. 30 3月, 2009 1 次提交
  9. 08 1月, 2009 1 次提交
  10. 04 12月, 2008 1 次提交
  11. 20 7月, 2008 1 次提交
  12. 15 7月, 2008 2 次提交
  13. 05 6月, 2008 1 次提交
  14. 25 4月, 2008 2 次提交
  15. 31 3月, 2008 1 次提交
  16. 03 2月, 2008 1 次提交
  17. 11 10月, 2007 1 次提交
  18. 10 10月, 2007 3 次提交
  19. 24 8月, 2007 1 次提交
    • M
      V4L/DVB (6070): Fix a warning at dvb_net · 04b35abe
      Mauro Carvalho Chehab 提交于
      static function dvb_net_sec declares input arg "pkt" as u8. However, the
      same argument at dvb_net_sec_callback is defined as "const u8". When
      calling dvb_net_sec, this is casted as just "u8".
      
      gcc 4.2.1 generates a warning about that:
      
        CC [M]  drivers/media/dvb/dvb-core/dvb_net.o
      drivers/media/dvb/dvb-core/dvb_net.c: In function "dvb_net_sec_callback":
      drivers/media/dvb/dvb-core/dvb_net.c:905: warning: passing argument 2 of
      		"dvb_net_sec" discards qualifiers from pointer target type
      Signed-off-by: NMauro Carvalho Chehab <mchehab@infradead.org>
      04b35abe
  20. 19 7月, 2007 1 次提交
  21. 28 4月, 2007 1 次提交
  22. 26 4月, 2007 3 次提交
  23. 28 12月, 2006 2 次提交
  24. 22 11月, 2006 1 次提交
  25. 25 6月, 2006 1 次提交
  26. 18 6月, 2006 1 次提交
    • H
      [NET]: Add netif_tx_lock · 932ff279
      Herbert Xu 提交于
      Various drivers use xmit_lock internally to synchronise with their
      transmission routines.  They do so without setting xmit_lock_owner.
      This is fine as long as netpoll is not in use.
      
      With netpoll it is possible for deadlocks to occur if xmit_lock_owner
      isn't set.  This is because if a printk occurs while xmit_lock is held
      and xmit_lock_owner is not set can cause netpoll to attempt to take
      xmit_lock recursively.
      
      While it is possible to resolve this by getting netpoll to use
      trylock, it is suboptimal because netpoll's sole objective is to
      maximise the chance of getting the printk out on the wire.  So
      delaying or dropping the message is to be avoided as much as possible.
      
      So the only alternative is to always set xmit_lock_owner.  The
      following patch does this by introducing the netif_tx_lock family of
      functions that take care of setting/unsetting xmit_lock_owner.
      
      I renamed xmit_lock to _xmit_lock to indicate that it should not be
      used directly.  I didn't provide irq versions of the netif_tx_lock
      functions since xmit_lock is meant to be a BH-disabling lock.
      
      This is pretty much a straight text substitution except for a small
      bug fix in winbond.  It currently uses
      netif_stop_queue/spin_unlock_wait to stop transmission.  This is
      unsafe as an IRQ can potentially wake up the queue.  So it is safer to
      use netif_tx_disable.
      
      The hamradio bits used spin_lock_irq but it is unnecessary as
      xmit_lock must never be taken in an IRQ handler.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      932ff279
  27. 07 2月, 2006 1 次提交
  28. 10 1月, 2006 2 次提交
  29. 13 12月, 2005 1 次提交
  30. 02 12月, 2005 1 次提交
  31. 10 9月, 2005 2 次提交