From: Christophe Saout <christophe@saout.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-net@vger.kernel.org, netdev@oss.sgi.com,
YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [BUG 2.6.12-rc4] IPv6 xfrm tunnel oops with large packets
Date: Sat, 21 May 2005 23:49:24 +0200 [thread overview]
Message-ID: <1116712164.10858.0.camel@leto.cs.pocnet.net> (raw)
In-Reply-To: <20050521194932.GA10959@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 121 bytes --]
Am Sonntag, den 22.05.2005, 05:49 +1000 schrieb Herbert Xu:
> Here is a minimal fix.
Yes, it fixes the problem.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-05-21 21:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1116702611.14509.10.camel@leto.cs.pocnet.net>
2005-05-21 19:49 ` [BUG 2.6.12-rc4] IPv6 xfrm tunnel oops with large packets Herbert Xu
2005-05-21 20:18 ` YOSHIFUJI Hideaki / 吉藤英明
2005-05-22 7:34 ` Herbert Xu
2005-05-23 20:11 ` David S. Miller
2005-05-21 21:49 ` Christophe Saout [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=1116712164.10858.0.camel@leto.cs.pocnet.net \
--to=christophe@saout.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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