netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <benh@debian.org>
To: Vladislav Zolotarov <vladz@broadcom.com>
Cc: Dave Miller <davem@davemloft.net>,
	netdev list <netdev@vger.kernel.org>,
	Eilon Greenstein <eilong@broadcom.com>
Subject: Re: [PATCH net-next 1/4] bnx2x: LSO code was broken on BE platforms
Date: Sun, 12 Dec 2010 04:14:53 +0000	[thread overview]
Message-ID: <1292127293.3136.261.camel@localhost> (raw)
In-Reply-To: <1291808589.30114.65.camel@lb-tlvb-vladz>

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

On Wed, 2010-12-08 at 13:43 +0200, Vladislav Zolotarov wrote:
> Make the LSO code work on BE platforms: parsing_data field of 
> a parsing BD (PBD) for 57712 was improperly composed which made FW read wrong 
> values for TCP header's length and offset and, as a result, the corresponding 
> PCI device was performing bad DMA reads triggering EEH.
[...]

This fix looks like it should go into the stable/longterm series.  Since
this driver has changed a lot since 2.6.32, you would need to provide a
backported patch for that.

Ben.

-- 
Ben Hutchings, Debian Developer and kernel team member


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  parent reply	other threads:[~2010-12-12  4:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08 11:43 [PATCH net-next 1/4] bnx2x: LSO code was broken on BE platforms Vladislav Zolotarov
2010-12-10  4:50 ` David Miller
2010-12-12  4:14 ` Ben Hutchings [this message]
2010-12-12 13:54   ` Vladislav Zolotarov

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=1292127293.3136.261.camel@localhost \
    --to=benh@debian.org \
    --cc=davem@davemloft.net \
    --cc=eilong@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=vladz@broadcom.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).