1. 10 12月, 2008 1 次提交
  2. 16 10月, 2008 1 次提交
  3. 26 7月, 2008 1 次提交
    • S
      firewire: avoid memleak after phy config transmit failure · c0220d68
      Stefan Richter 提交于
      Use only statically allocated data for PHY config packet transmission.
      With the previous incarnation, some data wouldn't be freed if the packet
      transmit callback was never called.
      
      A theoretical drawback now is that, in PCs with more than one card,
      card A may complete() for a waiter on card B.  But this is highly
      unlikely and its impact not serious.  Bus manager B may reset bus B
      before the PHY config went out, but the next phy config on B should be
      fine.  However, with a timeout of 100ms, this situation is close to
      impossible.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      c0220d68
  4. 14 7月, 2008 4 次提交
  5. 19 6月, 2008 2 次提交
    • S
      firewire: deadline for PHY config transmission · ae1e5355
      Stefan Richter 提交于
      If the low-level driver failed to initialize a card properly without
      noticing it, fw-core was blocked indefinitely when trying to send a
      PHY config packet.  This hung up the events kernel thread, e.g. locked
      up keyboard input.
      https://bugzilla.redhat.com/show_bug.cgi?id=444694
      https://bugzilla.redhat.com/show_bug.cgi?id=446763
      
      This problem was introduced between 2.6.25 and 2.6.26-rc1 by commit
      2a0a2590 "firewire: wait until PHY
      configuration packet was transmitted (fix bus reset loop)".
      
      The solution is to wait with timeout.  I tested it with 7 different
      working controllers and 1 non-working controller.  On the working ones,
      the packet callback complete()s usually --- but not always --- before a
      timeout of 10ms.  Hence I chose a safer timeout of 100ms.
      
      On the few tests with the non-working controller ALi M5271, PHY config
      packet transmission always timed out so far.  (Fw-ohci needs to be fixed
      for this controller independently of this deadline fix.  Often the core
      doesn't even attempt to send a phy config because not even self ID
      reception works.)
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      ae1e5355
    • S
      firewire: don't panic on invalid AR request buffer · 0bf607c5
      Stefan Richter 提交于
      BUG() at this place is wrong.  (Unless if the low level driver would
      already do higher-level input validation of incoming request headers.)
      
      Invalid incoming requests or bugs in the controller which corrupt the
      AR-req buffer needlessly crashed the box because this is run in tasklet
      context.
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      0bf607c5
  6. 19 4月, 2008 1 次提交
  7. 18 4月, 2008 4 次提交
  8. 21 3月, 2008 1 次提交
  9. 14 3月, 2008 1 次提交
    • S
      firewire: endianess annotations · efbf390a
      Stefan Richter 提交于
      Kills warnings from 'make C=1 CHECKFLAGS="-D__CHECK_ENDIAN__" modules':
      
      drivers/firewire/fw-transaction.c:771:10: warning: incorrect type in assignment (different base types)
      drivers/firewire/fw-transaction.c:771:10:    expected unsigned int [unsigned] [usertype] <noident>
      drivers/firewire/fw-transaction.c:771:10:    got restricted unsigned int [usertype] <noident>
      drivers/firewire/fw-transaction.h:93:10: warning: incorrect type in assignment (different base types)
      drivers/firewire/fw-transaction.h:93:10:    expected unsigned int [unsigned] [usertype] <noident>
      drivers/firewire/fw-transaction.h:93:10:    got restricted unsigned int [usertype] <noident>
      drivers/firewire/fw-ohci.c:1490:8: warning: restricted degrades to integer
      drivers/firewire/fw-ohci.c:1490:35: warning: restricted degrades to integer
      drivers/firewire/fw-ohci.c:1516:5: warning: cast to restricted type
      Signed-off-by: NStefan Richter <stefanr@s5r6.in-berlin.de>
      Signed-off-by: NJarod Wilson <jwilson@redhat.com>
      efbf390a
  10. 31 1月, 2008 2 次提交
  11. 20 10月, 2007 1 次提交
  12. 17 10月, 2007 1 次提交
  13. 03 8月, 2007 1 次提交
  14. 19 7月, 2007 2 次提交
  15. 11 5月, 2007 3 次提交
  16. 10 3月, 2007 14 次提交