All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Pavlic <fpavlic@de.ibm.com>
To: Jay Vosburgh <fubar@us.ibm.com>
Cc: jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: [PATCH 6/9] s390: qeth driver fixes [3/6]
Date: Fri, 15 Sep 2006 18:50:13 +0200	[thread overview]
Message-ID: <20060915165013.GA1375@de.ibm.com> (raw)
In-Reply-To: <200609151551.k8FFpPZt001753@death.nxdomain.ibm.com>

yes it would but the problem in qeth is not only bonding related.
We just have found it in a bonding scenario . But this kernel
panic could also occur without bonding. 

But thanks for reviewing it 
On Fri, Sep 15, 2006 at 08:51:25AM -0700, Jay Vosburgh wrote:
> Frank Pavlic <fpavlic@de.ibm.com> wrote:
> 
> >[PATCH 6/9] s390: qeth driver fixes [3/6]
> >
> >From: Frank Pavlic <fpavlic@de.ibm.com>
> >       	fixed kernel panic caused by qeth driver:
> >        Using a bonding device qeth driver will realloc
> >        headroom for every skb coming from the bond device.
> >        Once this happens qeth frees the original skb and
> >        set the skb pointer to the new realloced skb.
> 
> 	Frank, does the following patch to bonding (to track larger than
> usual hard_header_len) resolve this problem without changing qeth?  I
> believe this patch is queued for 2.6.19.
> 
> To: netdev@vger.kernel.org, bonding-devel@lists.sourceforge.net
> Cc: Jeff Garzik <jgarzik@pobox.com>
> Subject: [PATCH 5/7] bonding: Handle large hard_header_len
> X-Mailer: MH-E 7.83; nmh 1.1-RC4; GNU Emacs 21.4.1
> Date: Fri, 01 Sep 2006 15:12:44 -0700
> From: Jay Vosburgh <fubar@death>
> 
> 
> The bonding driver fails to adjust its hard_header_len when enslaving
> interfaces.  Whenever an interface with a hard_header_len greater than the
> ETH_HLEN default is enslaved, the potential for an oops exists, and if the
> oops happens while responding to an arp request, for example, the system
> panics.  GIANFAR devices may use an extended hard_header for VLAN or
> hardware checksumming.  Enslaving such a device and then transmitting over
> it causes a kernel panic.
> 
> Patch modified from submitter's original, but submitter agreed with this
> patch in private email.
> 
> Signed-off-by: Mark Huth <mhuth@mvista.com>
> Signed-off-by: Jay Vosburgh <fubar@us.ibm.com>
> 
> 
> --- netdev-2.6.git-upstream/drivers/net/bonding/bond_main.c	2006/08/19 14:46:07	1.3
> +++ netdev-2.6.git-upstream/drivers/net/bonding/bond_main.c	2006/08/19 15:47:27	1.4
> @@ -1211,10 +1211,14 @@ static int bond_compute_features(struct 
>  	unsigned long features = BOND_INTERSECT_FEATURES;
>  	struct slave *slave;
>  	struct net_device *bond_dev = bond->dev;
> +	unsigned short max_hard_header_len = ETH_HLEN;
>  	int i;
>  
> -	bond_for_each_slave(bond, slave, i)
> +	bond_for_each_slave(bond, slave, i) {
>  		features &= (slave->dev->features & BOND_INTERSECT_FEATURES);
> +		if (slave->dev->hard_header_len > max_hard_header_len)
> +			max_hard_header_len = slave->dev->hard_header_len;
> +	}
>  
>  	if ((features & NETIF_F_SG) && 
>  	    !(features & NETIF_F_ALL_CSUM))
> @@ -1232,6 +1236,7 @@ static int bond_compute_features(struct 
>  
>  	features |= (bond_dev->features & ~BOND_INTERSECT_FEATURES);
>  	bond_dev->features = features;
> +	bond_dev->hard_header_len = max_hard_header_len;
>  
>  	return 0;
>  }
> 
> 
> 
> 	-J
> 
> ---
> 	-Jay Vosburgh, IBM Linux Technology Center, fubar@us.ibm.com

  reply	other threads:[~2006-09-15 16:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 14:26 [PATCH 6/9] s390: qeth driver fixes [3/6] Frank Pavlic
2006-09-15 15:51 ` Jay Vosburgh
2006-09-15 16:50   ` Frank Pavlic [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-09-06 15:05 fpavlic

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060915165013.GA1375@de.ibm.com \
    --to=fpavlic@de.ibm.com \
    --cc=fubar@us.ibm.com \
    --cc=jgarzik@pobox.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.