[openib-general] tcpdump command issue on IB network

[Scott Weitzenkamp (sweitzen)]

Thanks, but most of our IB customers will want to use a stock RHEL4
kernel, so that's what our SQA has to test with.

Scott 

> -----Original Message-----
> From: Bob Woodruff [mailto:robert.j.woodruff at intel.com] 
> Sent: Tuesday, April 11, 2006 2:04 PM
> To: Scott Weitzenkamp (sweitzen); Roland Dreier (rdreier)
> Cc: Jerome Taylor; openib-general at openib.org
> Subject: RE: [openib-general] tcpdump command issue on IB network
> 
> Scott wrote, 
> >Bummer, there's no way to get just a tcpdump binary that 
> will work with
> >RHEL4 kernel?
> 
> >Scott
> 
> You can also apply this patch to your RHEL4 kernel source and 
> rebuild the
> kernel.
> 
> 
> diff -Naurp linux-2.6.9/net/core/dev.c 
> linux-2.6.9-fixups/net/core/dev.c
> --- linux-2.6.9/net/core/dev.c  2006-04-11 10:38:26.000000000 -0700
> +++ linux-2.6.9-fixups/net/core/dev.c   2006-04-11 
> 10:41:03.000000000 -0700
> @@ -2304,8 +2304,6 @@ static int dev_ifsioc(struct ifreq *ifr,
>                         return dev_set_mtu(dev, ifr->ifr_mtu);
> 
>                 case SIOCGIFHWADDR:
> -                       if ((size_t) dev->addr_len > sizeof
> ifr->ifr_hwaddr.sa_data)
> -                               return -EOVERFLOW;
>                         memset(ifr->ifr_hwaddr.sa_data, 0, sizeof
> ifr->ifr_hwaddr.sa_data);
>                         memcpy(ifr->ifr_hwaddr.sa_data, dev->dev_addr,
> dev->addr_len);
>                         ifr->ifr_hwaddr.sa_family = dev->type;
> ~
>