1. 07 5月, 2008 1 次提交
    • B
      [netdrvr] eexpress: IPv6 fails - multicast problems · 46fa0617
      Bruce Robson 提交于
      Taken from http://bugzilla.kernel.org/show_bug.cgi?id=10577
      
      I was unable to access a computer containing an Intel EtherExpress 16 network
      card using IPv6.
      
      I traced this to failure of neighbour discovery.  When I used an "ip -6 neigh
      add" command, on the computer attempting access, to insert a binding between
      the IPv6 address of the computer with the Intel EtherExpress 16 network card
      and the card's ethernet address, I was able to access that computer using
      IPv6.
      
      Neighbour discovery requires working multicast.  The driver sources file
      eexpress.c contains an approximately 30 line function eexp_setup_filter used
      when loading multicast addresses.
      
      I found 3 problems in this function
      
      1) It wrote the number of multicast addresses to the card instead of the
          number of bytes in the multicast addresses.
      
      2) When loading multiple multicast addresses it loaded the first one
          provided multiple times instead of loading each one once.
      
      3) The setting of pointer 'data' from 'dmi->dmi_addr' occured before the
          test for the error situation of 'dmi' being NULL.
      
      Correcting these problems allows the computer with the Intel EtherExpress 16
      network card to found by IPv6 neighbour discovery.
      
      p.s. There is some information on the Intel EtherExpress 16 at
      http://www.intel.com/support/etherexpress/vintage/sb/cs-013500.htm
      Datasheet for the Intel 82586 ethernet controller used by the card
      http://www.datasheetcatalog.com/datasheets_pdf/8/2/5/8/82586.shtmlSigned-off-by: NBruce Robson <bns_robson@hotmail.com>
      Cc: Jeff Garzik <jeff@garzik.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NJeff Garzik <jgarzik@redhat.com>
      46fa0617
  2. 03 2月, 2008 1 次提交
  3. 29 1月, 2008 2 次提交
  4. 24 10月, 2007 1 次提交
  5. 11 10月, 2007 2 次提交
  6. 28 4月, 2007 2 次提交
  7. 26 4月, 2007 1 次提交
  8. 18 2月, 2007 1 次提交
  9. 05 12月, 2006 1 次提交
  10. 07 10月, 2006 1 次提交
  11. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells 提交于
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
      of passing regs around manually through all ~1800 interrupt handlers in the
      Linux kernel.
      
      The regs pointer is used in few places, but it potentially costs both stack
      space and code to pass it around.  On the FRV arch, removing the regs parameter
      from all the genirq function results in a 20% speed up of the IRQ exit path
      (ie: from leaving timer_interrupt() to leaving do_IRQ()).
      
      Where appropriate, an arch may override the generic storage facility and do
      something different with the variable.  On FRV, for instance, the address is
      maintained in GR28 at all times inside the kernel as part of general exception
      handling.
      
      Having looked over the code, it appears that the parameter may be handed down
      through up to twenty or so layers of functions.  Consider a USB character
      device attached to a USB hub, attached to a USB controller that posts its
      interrupts through a cascaded auxiliary interrupt controller.  A character
      device driver may want to pass regs to the sysrq handler through the input
      layer which adds another few layers of parameter passing.
      
      I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
      main part of the code on FRV and i386, though I can't test most of the drivers.
      I've also done partial conversion for powerpc and MIPS - these at least compile
      with minimal configurations.
      
      This will affect all archs.  Mostly the changes should be relatively easy.
      Take do_IRQ(), store the regs pointer at the beginning, saving the old one:
      
      	struct pt_regs *old_regs = set_irq_regs(regs);
      
      And put the old one back at the end:
      
      	set_irq_regs(old_regs);
      
      Don't pass regs through to generic_handle_irq() or __do_IRQ().
      
      In timer_interrupt(), this sort of change will be necessary:
      
      	-	update_process_times(user_mode(regs));
      	-	profile_tick(CPU_PROFILING, regs);
      	+	update_process_times(user_mode(get_irq_regs()));
      	+	profile_tick(CPU_PROFILING);
      
      I'd like to move update_process_times()'s use of get_irq_regs() into itself,
      except that i386, alone of the archs, uses something other than user_mode().
      
      Some notes on the interrupt handling in the drivers:
      
       (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
           the input_dev struct.
      
       (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
           something different depending on whether it's been supplied with a regs
           pointer or not.
      
       (*) Various IRQ handler function pointers have been moved to type
           irq_handler_t.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  12. 14 9月, 2006 1 次提交
  13. 20 8月, 2006 1 次提交
    • A
      [PATCH] eexpress section fix · b1176b95
      Andrew Morton 提交于
      WARNING: drivers/net/eexpress.o - Section mismatch: reference to .init.text: from .text between 'init_module' (at offset 0x6c3) and 'eexp_hw_lasttxstat'
      WARNING: drivers/net/eexpress.o - Section mismatch: reference to .init.text: from .text between 'init_module' (at offset 0x74f) and 'eexp_hw_lasttxstat'
      
      Cc: Jeff Garzik <jeff@garzik.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NJeff Garzik <jeff@garzik.org>
      b1176b95
  14. 01 7月, 2006 1 次提交
  15. 23 6月, 2006 1 次提交
    • H
      [NET]: Avoid allocating skb in skb_pad · 5b057c6b
      Herbert Xu 提交于
      First of all it is unnecessary to allocate a new skb in skb_pad since
      the existing one is not shared.  More importantly, our hard_start_xmit
      interface does not allow a new skb to be allocated since that breaks
      requeueing.
      
      This patch uses pskb_expand_head to expand the existing skb and linearize
      it if needed.  Actually, someone should sift through every instance of
      skb_pad on a non-linear skb as they do not fit the reasons why this was
      originally created.
      
      Incidentally, this fixes a minor bug when the skb is cloned (tcpdump,
      TCP, etc.).  As it is skb_pad will simply write over a cloned skb.  Because
      of the position of the write it is unlikely to cause problems but still
      it's best if we don't do it.
      Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5b057c6b
  16. 13 5月, 2005 1 次提交
  17. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4