netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Kazunori Miyazawa <kazunori@miyazawa.org>
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com, usagi@linux-ipv6.org,
	latten@austin.ibm.com
Subject: Re: [PATCH][IPV6] fixed authentication error with TCP
Date: Thu, 7 Aug 2003 22:05:39 -0700	[thread overview]
Message-ID: <20030807220539.4555db2d.davem@redhat.com> (raw)
In-Reply-To: <20030806164413.669ef5f8.kazunori@miyazawa.org>

On Wed, 6 Aug 2003 16:44:13 +0900
Kazunori Miyazawa <kazunori@miyazawa.org> wrote:

> Miss Joy (@IBM) and I investigated the bug that "authentication
> error" occured with using TCP and AH in IPv6. This patch fixes the
> bug. This patch makes the kernel consider extension header length in
> a dst.
> 
> This pach works with my previous patch which fixes zero-clear in ah6_input.
> 
> Please append the name "Joy Latten" into the log.

I have applied this patch, thank you.

But I see a small area for improvement.  Look at the place inside
of ip6_dst_lookup() where we do source address selection.  If this
fails, we mark error to dst->error.

Is it correct?  This 'dst' route might otherwise be perfectly fine.
But now that dst->error is set, it is poisoned for other users
and they are not able to use it.

A similar case occurs further down after the xfrm_lookup() call, but
this one I think is correct.

It seems to me that it is only OK for dst->error to be set on routes
that may not be used validly for anything.

Alexey, do I understand this stuff correctly?

  reply	other threads:[~2003-08-08  5:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-06  7:44 [PATCH][IPV6] fixed authentication error with TCP Kazunori Miyazawa
2003-08-08  5:05 ` David S. Miller [this message]
2003-08-17 23:29   ` kuznet
2003-08-18  7:45     ` Ville Nuorvala
2003-08-18  7:45       ` David S. Miller
2003-08-18  9:32       ` Kazunori Miyazawa
2003-08-18  9:48       ` David S. Miller
2003-08-18 10:36         ` David S. Miller
2003-08-18 10:11       ` David S. Miller

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=20030807220539.4555db2d.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=kazunori@miyazawa.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=latten@austin.ibm.com \
    --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).