Skip to content
Snippets Groups Projects
  1. Dec 08, 2009
    • Stanislav Brabec's avatar
      b44 WOL setup: one-bit-off stack corruption kernel panic fix · e0188829
      Stanislav Brabec authored
      
      About 50% of shutdowns of b44 Ethernet adapter ends by kernel panic
      with kernels compiled with stack-protector.
      
      Checking b44_magic_pattern() return values, one call of
      b44_magic_pattern() returns 127. It means, that set_bit(128, pmask)
      was called on line 1509. It means that bit 0 of 17th byte of pmask was
      overwritten. But pmask has only 16 bytes. Stack corruption happens.
       
      It seems that set_bit() on line 1509 always writes one bit off.
      
      The fix does not only solve the stack corruption, but also makes Wake
      On LAN working on my onboard B44 on Asus A7V-333X mainboard.
      
      It seems that this problem affects all kernel versions since commit
      725ad800 ([PATCH] b44: add wol for old nic) on 2006-06-20.
      
      Signed-off-by: default avatarStanislav Brabec <sbrabec@suse.cz>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      e0188829
  2. Nov 30, 2009
  3. Sep 16, 2009
  4. Sep 09, 2009
  5. Sep 01, 2009
  6. Aug 14, 2009
  7. Aug 02, 2009
  8. Jul 20, 2009
  9. May 27, 2009
  10. Apr 07, 2009
  11. Apr 06, 2009
  12. Apr 04, 2009
    • Michael Buesch's avatar
      b44: Fix sizes passed to b44_sync_dma_desc_for_{device,cpu}() · 5d4d9e8a
      Michael Buesch authored
      
      > > ------------[ cut here ]------------
      > > WARNING: at lib/dma-debug.c:539 check_sync+0xe9/0x341() (Not tainted)
      > > Hardware name: HP Compaq nx6110 (PY501EA#AB9)
      > > b44 0000:02:0e.0: DMA-API: device driver tries to sync DMA memory it has not
      > > allocated [device address=0x0000000075941040] [size=1566 bytes]
      > > Modules linked in: llc bnep l2cap bluetooth autofs4 lm90 hwmon i2c_i801 sunrpc
      > > ipv6 cpufreq_ondemand acpi_cpufreq uinput snd_intel8x0m snd_intel8x0
      > > snd_ac97_codec snd_seq_dummy ac97_bus snd_seq_oss snd_seq_midi_event snd_seq
      > > snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm b44 ssb firewire_ohci
      > > snd_timer ipw2200 iTCO_wdt mii firewire_core snd iTCO_vendor_support libipw
      > > yenta_socket crc_itu_t lib80211 rsrc_nonstatic soundcore snd_page_alloc joydev
      > > pcspkr wmi serio_raw ata_generic pata_acpi i915 drm i2c_algo_bit i2c_core video
      > > output [last unloaded: scsi_wait_scan]
      > > Pid: 2418, comm: S58ntpd Not tainted 2.6.29-16.fc10.i686.PAE #1
      > > Call Trace:
      > >  [<c04396d1>] warn_slowpath+0x7c/0xbd
      > >  [<c0457fe1>] ? register_lock_class+0x17/0x290
      > >  [<c0458d61>] ? mark_lock+0x1e/0x349
      > >  [<c0556448>] ? _raw_spin_unlock+0x74/0x78
      > >  [<c0458d61>] ? mark_lock+0x1e/0x349
      > >  [<c055a060>] ? check_sync+0x37/0x341
      > >  [<c055a112>] check_sync+0xe9/0x341
      > >  [<c0711245>] ? _spin_unlock_irqrestore+0x45/0x55
      > >  [<c04592db>] ? trace_hardirqs_on+0xb/0xd
      > >  [<c055a4d1>] debug_dma_sync_single_for_device+0x2f/0x39
      > >  [<f828f722>] dma_sync_single_for_device+0x4a/0x59 [b44]
      > >  [<f828f76f>] ssb_dma_sync_single_for_device+0x3e/0x48 [b44]
      > >  [<f8291d1e>] b44_recycle_rx+0x18c/0x196 [b44]
      > >  [<f8291f9f>] b44_poll+0x277/0x3c0 [b44]
      > >  [<c0687bb9>] net_rx_action+0xa1/0x1ca
      > >  [<c043e30a>] __do_softirq+0x9d/0x154
      > >  [<c043e413>] do_softirq+0x52/0x7e
      > >  [<c043e56f>] irq_exit+0x49/0x77
      > >  [<c040b22e>] do_IRQ+0x97/0xad
      > >  [<c0409dac>] common_interrupt+0x2c/0x34
      
      I don't know if this is related, but the following patch seems to fix some DMA
      mapping bug. Can somebody comment who does understand the code better than me?
      
      (completely untested)
      
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      5d4d9e8a
  13. Feb 26, 2009
  14. Feb 10, 2009
  15. Jan 21, 2009
  16. Jan 15, 2009
    • Eric Dumazet's avatar
      b44: GFP_DMA skb should not escape from driver · a58c891a
      Eric Dumazet authored
      
      b44 chip has some hardware limitations, that need GFP_DMA bounce
      buffers in some situations.
      
      In order to not deplete DMA zone, we should keep allocated GFP_DMA skb
      only for driver use. At rx time, we copy such skb to newly allocated
      skb, reusing existing copybreak infrastructure.
      
      On machines with low amount of memory, all skb meet the hardware limitation,
      so no copy is needed. We detect this situation using a new device flag, set
      to one if one GFP_DMA skb was ever allocated by b44_alloc_rx_skb().
      
      Previously allocated skb, even outside from DMA zone will then be recycled,
      to have minimal impact on DMA zone use.
      
      Signed-off-by: default avatarEric Dumazet <dada1@cosmosbay.com>
      Tested-by: default avatarIonut Leonte <ionut.leonte@gmail.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      a58c891a
  17. Jan 11, 2009
    • Felix Fietkau's avatar
      b44: fix misalignment and wasted space in rx handling · 4ca85795
      Felix Fietkau authored
      
      Broadcom 4400 puts a header of configurable size (apparently needs
      to be at least 28 bytes) in front of received packets. When handling
      this, the previous code accidentally added the offset 30 *twice* for
      the software and once for the hardware, thereby cancelling out the
      IP alignment effect of the 30 byte padding and wasting an additional
      30 bytes of memory per packet.
      
      This patch fixes this problem and improves routing throughput by
      about 30% on MIPS, where unaligned access is expensive.
      
      Signed-off-by: default avatarFelix Fietkau <nbd@openwrt.org>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      4ca85795
  18. Jan 07, 2009
  19. Dec 26, 2008
  20. Dec 22, 2008
  21. Nov 03, 2008
  22. Oct 27, 2008
  23. Jun 27, 2008
  24. Apr 15, 2008
    • Michael Buesch's avatar
      ssb: Fix usage of struct device used for DMAing · 4ac58469
      Michael Buesch authored
      
      This fixes DMA on architectures where DMA is nontrivial, like PPC64.
      We must use the host-device's (PCI) struct device for any DMA
      operation instead of the SSB device. For this we add a new
      struct device pointer to the SSB device structure that will always
      point to the right device for DMAing.
      
      Without this patch b43 and b44 drivers won't work on complex-DMA
      architectures, that for example need dev->archdata for DMA operations.
      
      Signed-off-by: default avatarMichael Buesch <mb@bu3sch.de>
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      4ac58469
  25. Mar 25, 2008
    • Michael Buesch's avatar
      b44: Truncate PHY address · 5ea79631
      Michael Buesch authored
      
      Some ROMs on embedded devices store incorrect values for
      the PHY address of the ethernet device.
      It looks like the number is sign-extended.
      Truncate the value by applying the PHY-address mask to it.
      The patch was tested on a bcm47xx embedded system (where the bug
      triggers) and a bcm4400 PCI card.
      
      Signed-off-by: default avatarMichael Buesch <mb@bu3sch.de>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
      5ea79631
  26. Jan 28, 2008
  27. Oct 10, 2007
  28. Jul 31, 2007
  29. Jul 19, 2007
  30. Jul 08, 2007
  31. Apr 25, 2007
Loading