netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shan Wei <shanwei@cn.fujitsu.com>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [RFC][PATCH 3/3] IPv4:Check IP_MULTICAST_LOOP option value
Date: Tue, 10 Jun 2008 17:07:34 +0800	[thread overview]
Message-ID: <484E4456.4040206@cn.fujitsu.com> (raw)
In-Reply-To: <20080610.174202.32087382.yoshfuji@linux-ipv6.org>

YOSHIFUJI Hideaki / 吉藤英明 写道:
> In article <484E3C0A.1000808@cn.fujitsu.com> (at Tue, 10 Jun 2008 16:32:10 +0800), Shan Wei <shanwei@cn.fujitsu.com> says:
> 
>> YOSHIFUJI Hideaki / 吉藤英明 写道:
>>> In article <484E3293.8000507@cn.fujitsu.com> (at Tue, 10 Jun 2008 15:51:47 +0800), Shan Wei <shanwei@cn.fujitsu.com> says:
>>>
>>>> The IP_MULTICAST_LOOP option can only be set with o or 1. When 
>>>> other valuse are set, the kernel should return an error of EINVAL.
>>>>
>>>> In addition, the option should not be uesd by SOCK_STREAM type,
>>>> same as IP_MULTICAST_IF, IP_MULTICAST_TTL.
>>>>   
>>>> But the kernel doesn't check them.
>>> Is there any standard reference about this?
>>>
>> I have not found it.
>> But, the IP_MULTICAST_LOOP option is same as IPV6_MULTICAST_LOOP.
> 
> I disagree.
> We follow what traditional BSDs do, and they do not check if the
> value is 0 or 1 for IP_MULTICAST_LOOP.
> On the other hand, they do for IPV6_MULTICAST_LOOP.
> 
Ok.
no need to check "val".

The option should not be uesd by SOCK_STREAM type.
how do you think of ?
> --yoshfuji
> 
> 
> 


-- 
Regards
単 衛
--------------------------------------------------
Shan Wei
Development Dept.I

Nanjing Fujitsu Nanda Software Tech. Co., Ltd.(FNST)
8/F., Civil Defense Building, No.189 Guangzhou Road,
Nanjing, 210029, China
TEL:+86+25-86630566-836
FUJITSU INTERNAL:79955-836
FAX:+86+25-83317685
Mail:shanwei@cn.fujitsu.com
--------------------------------------------------
This communication is for use by the intended recipient(s) only and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not an intended recipient of this communication, you are hereby notified that any dissemination, distribution or copying hereof is strictly prohibited.  If you have received this communication in error, please notify me by reply e-mail, permanently delete this communication from your system, and destroy any hard copies you may have printed.


      reply	other threads:[~2008-06-10  9:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  7:51 [RFC][PATCH 3/3] IPv4:Check IP_MULTICAST_LOOP option value Shan Wei
2008-06-10  8:15 ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-10  8:32   ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-10  8:32   ` Shan Wei
2008-06-10  8:42     ` YOSHIFUJI Hideaki / 吉藤英明
2008-06-10  9:07       ` Shan Wei [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=484E4456.4040206@cn.fujitsu.com \
    --to=shanwei@cn.fujitsu.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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 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).