From: "David S. Miller" <davem@redhat.com>
To: mk@linux-ipv6.org
Cc: netdev@oss.sgi.com, usagi@linux-ipv6.org
Subject: Re: [PATCH] fix esp6 extension headers handling
Date: Sat, 07 Jun 2003 02:22:41 -0700 (PDT) [thread overview]
Message-ID: <20030607.022241.98862720.davem@redhat.com> (raw)
In-Reply-To: <87wufzxe8p.wl@karaba.org>
From: Mitsuru KANDA / 神田 充 <mk@linux-ipv6.org>
Date: Sat, 07 Jun 2003 03:17:10 +0900
The attached diff fixes esp6 extension headers handling bug
which reported by Henrik.
I introduced ip6_find_1stfragopt() instead of get_offset().
# ip6_found_nexthdr() is just renamed ip6_find_1stfragopt()
# in order to represent collect functionality.
Patch applied, thank you.
prev parent reply other threads:[~2003-06-07 9:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 12:25 Bug in ipv6 ipsec in handling of packets with extension headers Henrik Petander
2003-06-05 12:17 ` David S. Miller
2003-06-05 12:59 ` Henrik Petander
2003-06-05 16:54 ` Mitsuru KANDA / 神田 充
2003-06-06 18:17 ` [PATCH] fix esp6 extension headers handling Mitsuru KANDA / 神田 充
2003-06-07 9:22 ` David S. 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=20030607.022241.98862720.davem@redhat.com \
--to=davem@redhat.com \
--cc=mk@linux-ipv6.org \
--cc=netdev@oss.sgi.com \
--cc=usagi@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;
as well as URLs for NNTP newsgroup(s).