netdev - Re: [PATCH] IPv6:fix the return interface index when get it while no message is received

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48AA6800.1020506@cn.fujitsu.com>
Date:	Tue, 19 Aug 2008 14:28:16 +0800
From:	Yang Hongyang <yanghy@...fujitsu.com>
To:	David Miller <davem@...emloft.net>
CC:	vladislav.yasevich@...com, netdev@...r.kernel.org,
	yoshfuji@...ux-ipv6.org
Subject: Re: [PATCH] IPv6:fix the return interface index when get it while
 no message is received

David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@...com>
> Date: Mon, 18 Aug 2008 09:31:07 -0400
> 
>> I don't think that's correct at all.  The code path shows here is
>> when there are no received options and no sticky options set.  In
>> such case, we shouldn't be returning multicast or bound interfaces.
>> We should be returning 0.

I use setsockopt() to set the bounded interface of the socket, and 
then I get receiving interface index while no message is received through
the above socket,shoudn't the bounded interface be returned?

>>
>> Additionally the address returned is completely bogus as well. We
>> are returning the address our peer instead of the one of our own
>> addresses.

If message is received,the address returned is what the received
message refered to, otherwise the address returned is what I used setsockopt()
to set before.

> 
> Yang, please fix this up, thank you.
> 
> 

Seems that I misunderstood the RFC?
--
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