1. 03 Nov, 2008 3 commits
    • David S. Miller's avatar
      SMC91x: Fix compilation on some platforms. · 55c8eb6c
      David S. Miller authored
      This reverts 51ac3bef ('SMC91x: delete
      unused local variable "lp"') and adds __maybe_unused markers to these
      (potentially) unused variables.
      
      The issue is that in some configurations SMC_IO_SHIFT evaluates
      to '(lp->io_shift)', but in some others it's plain '0'.
      
      Based upon a build failure report from Manuel Lauss.
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      55c8eb6c
    • Wei Yongjun's avatar
      udp: Fix the SNMP counter of UDP_MIB_INERRORS · 0856f939
      Wei Yongjun authored
      UDP packets received in udpv6_recvmsg() are not only IPv6 UDP packets, but
      also have IPv4 UDP packets, so when do the counter of UDP_MIB_INERRORS in
      udpv6_recvmsg(), we should check whether the packet is a IPv6 UDP packet
      or a IPv4 UDP packet.
      Signed-off-by: default avatarWei Yongjun <yjwei@cn.fujitsu.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      0856f939
    • Wei Yongjun's avatar
      udp: Fix the SNMP counter of UDP_MIB_INDATAGRAMS · f26ba175
      Wei Yongjun authored
      If UDP echo is sent to xinetd/echo-dgram, the UDP reply will be received
      at the sender. But the SNMP counter of UDP_MIB_INDATAGRAMS will be not
      increased, UDP6_MIB_INDATAGRAMS will be increased instead.
      
        Endpoint A                      Endpoint B
        UDP Echo request ----------->
        (IPv4, Dst port=7)
                         <----------    UDP Echo Reply
                                        (IPv4, Src port=7)
      
      This bug is come from this patch cb75994e.
      
      It do counter UDP[6]_MIB_INDATAGRAMS until udp[v6]_recvmsg. Because
      xinetd used IPv6 socket to receive UDP messages, thus, when received
      UDP packet, the UDP6_MIB_INDATAGRAMS will be increased in function
      udpv6_recvmsg() even if the packet is a IPv4 UDP packet.
      
      This patch fixed the problem.
      Signed-off-by: default avatarWei Yongjun <yjwei@cn.fujitsu.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      f26ba175
  2. 02 Nov, 2008 5 commits
  3. 31 Oct, 2008 30 commits
  4. 30 Oct, 2008 2 commits
    • Ingo Molnar's avatar
      x86: cpu_index build fix · 1c4acdb4
      Ingo Molnar authored
      fix:
      
       arch/x86/kernel/cpu/common.c: In function 'early_identify_cpu':
       arch/x86/kernel/cpu/common.c:553: error: 'struct cpuinfo_x86' has no member named 'cpu_index'
      
      as cpu_index is only available on SMP.
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      1c4acdb4
    • James Bottomley's avatar
      x86/voyager: fix missing cpu_index initialisation · bfcb4c1b
      James Bottomley authored
      Impact: fix /proc/cpuinfo output on x86/Voyager
      
      Ever since
      
      | commit 92cb7612
      | Author: Mike Travis <travis@sgi.com>
      | Date:   Fri Oct 19 20:35:04 2007 +0200
      |
      |     x86: convert cpuinfo_x86 array to a per_cpu array
      
      We've had an extra field in cpuinfo_x86 which is cpu_index.
      Unfortunately, voyager has never initialised this, although the only
      noticeable impact seems to be that /proc/cpuinfo shows all zeros for
      the processor ids.
      
      Anyway, fix this by initialising the boot CPU properly and setting the
      index when the secondaries update.
      Signed-off-by: default avatarJames Bottomley <James.Bottomley@HansenPartnership.com>
      Signed-off-by: default avatarIngo Molnar <mingo@elte.hu>
      bfcb4c1b