All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com, usagi@linux-ipv6.org
Subject: Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port
Date: Thu, 03 Oct 2002 08:04:08 -0700 (PDT)	[thread overview]
Message-ID: <20021003.080408.78030688.davem@redhat.com> (raw)
In-Reply-To: <20021004.000631.28088811.yoshfuji@linux-ipv6.org>

   From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
   Date: Fri, 04 Oct 2002 00:06:31 +0900 (JST)

   In article <20021003.231534.83777766.yoshfuji@linux-ipv6.org> (at Thu, 03 Oct 2002 23:15:34 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org> says:
   
   > In article <200210031301.RAA29267@sex.inr.ac.ru> (at Thu, 3 Oct 2002 17:01:11 +0400 (MSD)), kuznet@ms2.inr.ac.ru says:
   > 
   > > While doing *_get_port() daddr/dport are _unknown_ and always zero,
   > > so it never works.
   > > 
   > > Please, remove these bits, the patch will become simpler.
   > 
   > Ok, I'll do that.
   
   I remember that test for daddr is for existing sockets, 
   not for socket doing XXX_get_port().
   So, I think I don't need to remove that.

Where can daddr/dport be non-zero during get_port()?

  reply	other threads:[~2002-10-03 15:04 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03  3:13 [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port Number (IPV6_V6ONLY Support) YOSHIFUJI Hideaki / 吉藤英明
2002-10-03  3:53 ` acme
2002-10-03  3:55 ` acme
2002-10-03  7:00 ` Pekka Savola
2002-10-03  8:29 ` David S. Miller
2002-10-03  8:55   ` Brad Hards
2002-10-03  8:58     ` David S. Miller
2002-10-03 13:06   ` [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same kuznet
2002-10-03 13:02     ` David S. Miller
2002-10-03 13:18       ` Pekka Savola
2002-10-03 13:13         ` David S. Miller
2002-10-03 13:01 ` [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port kuznet
2002-10-03 14:15   ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 14:10     ` David S. Miller
2002-10-03 15:06     ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 15:04       ` David S. Miller [this message]
2002-10-03 15:19         ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-03 15:52           ` kuznet
2002-10-23  7:24             ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port) YOSHIFUJI Hideaki / 吉藤英明
2002-10-23  7:23               ` David S. Miller
2002-10-23  7:58                 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23  8:06                   ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23  8:02                     ` David S. Miller
2002-10-23  7:36               ` Pekka Savola
2002-10-23 10:01                 ` YOSHIFUJI Hideaki / 吉藤英明
2002-10-23 10:15                   ` Pekka Savola
2002-10-23 10:12                     ` David S. Miller
2002-10-24 16:24                     ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both kuznet
2002-10-25  7:46                       ` Pekka Savola
2002-10-23 15:53               ` [PATCH] IPV6_V6ONLY Support, v2 (is Re: [PATCH] IPv6: Allow Both IPv6 and IPv4 Sockets on the Same Port) Kyle C Quest
2002-10-23 16:06                 ` Pekka Savola
2002-10-23 16:09                   ` Kyle C Quest
2002-10-24 10:24               ` 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=20021003.080408.78030688.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@oss.sgi.com \
    --cc=usagi@linux-ipv6.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.