netdev - Re: [PATCH RESEND] ipv6: return with appropriate error code when sending RH0 using setsockopt()

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 for Android: free password hash cracker in your pocket

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

Message-ID: <48BE5BCB.6090404@cn.fujitsu.com>
Date:	Wed, 03 Sep 2008 17:41:31 +0800
From:	Shan Wei <shanwei@...fujitsu.com>
To:	David Miller <davem@...emloft.net>
CC:	netdev@...r.kernel.org
Subject: Re: [PATCH RESEND] ipv6: return with appropriate error code when
 sending RH0 using setsockopt()

David Miller 写道:
> From: Shan Wei <shanwei@...fujitsu.com>
> Date: Wed, 03 Sep 2008 16:41:06 +0800
> 
>>  I'm sorry to resend the patch, for that no one replied it from Jun 27.
>>
>>  The kernel had removed the RH0(Type 0 Routing Header), but we can still
>>  send IPv6 packet with RH0 using sendmsg() or setsockopt().
>>
>>  Compare with sendmsg() that returns EINVAL, but setsockopt() return EPERM.
>>  The patch fix it.
>>
>> Signed-off-by: Shan Wei <shanwei@...fujitsu.com>
> 
> I've tried to defer IPV6 patches that have semantic issues to an
> expert such as Yoshifuji-san, but he has dropped off the face of the
> planet for a while.
> 
> I'll take a look at this if I get a chance.
> 
thanks for your so fast reply。
I'm patient to wait for your ack.

--
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