[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080610.173206.02155080.yoshfuji@linux-ipv6.org>
Date: Tue, 10 Jun 2008 17:32:06 +0900 (JST)
From: YOSHIFUJI Hideaki / 吉藤英明
<yoshfuji@...ux-ipv6.org>
To: shanwei@...fujitsu.com
Cc: davem@...emloft.net, netdev@...r.kernel.org,
yoshfuji@...ux-ipv6.org
Subject: Re: [RFC][PATCH 3/3] IPv4:Check IP_MULTICAST_LOOP option value
In article <20080610.171527.86317043.yoshfuji@...ux-ipv6.org> (at Tue, 10 Jun 2008 17:15:27 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@...ux-ipv6.org> says:
> In article <484E3293.8000507@...fujitsu.com> (at Tue, 10 Jun 2008 15:51:47 +0800), Shan Wei <shanwei@...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?
And actually I diagree to check "val."
(For example, FreeBSD does not check this.)
--yoshfuji
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists