netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: herbert@gondor.apana.org.au
Cc: netdev@vger.kernel.org
Subject: Re: bridge: Fix LRO crash with tun
Date: Mon, 09 Feb 2009 15:07:37 -0800 (PST)	[thread overview]
Message-ID: <20090209.150737.08510604.davem@davemloft.net> (raw)
In-Reply-To: <20090209100253.GA7232@gondor.apana.org.au>

From: Herbert Xu <herbert@gondor.apana.org.au>
Date: Mon, 9 Feb 2009 21:02:53 +1100

> bridge: Fix LRO crash with tun
 ...
> This crashed when an LRO packet generated by bnx2x reached a
> tun device through the bridge.  We're supposed to drop it at
> the bridge.  However, because the check was placed in br_forward
> instead of __br_forward, it's only effective if we are sending
> the packet through a single port.
> 
> This patch fixes it by moving the check into __br_forward.
> 
> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>

Applied, thanks a lot Herbert.

      reply	other threads:[~2009-02-09 23:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 10:02 bridge: Fix LRO crash with tun Herbert Xu
2009-02-09 23:07 ` David Miller [this message]

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=20090209.150737.08510604.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --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 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).