From mboxrd@z Thu Jan  1 00:00:00 1970
From: David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next] ipv6: raw: use IPv4 raw_sendmsg on v4-mapped
 IPv6 destinations
Date: Thu, 25 Jan 2018 12:07:12 -0500 (EST)
Message-ID: <20180125.120712.993712764993225765.davem@davemloft.net>
References: <20180125014343.GA19881@visor>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: netdev@vger.kernel.org
To: colona@arista.com
Return-path: <netdev-owner@vger.kernel.org>
Received: from shards.monkeyblade.net ([184.105.139.130]:59622 "EHLO
        shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1750994AbeAYRHN (ORCPT
        <rfc822;netdev@vger.kernel.org>); Thu, 25 Jan 2018 12:07:13 -0500
In-Reply-To: <20180125014343.GA19881@visor>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

From: Ivan Delalande <colona@arista.com>
Date: Wed, 24 Jan 2018 17:43:43 -0800

> Make IPv6 SOCK_RAW sockets operate like IPv6 UDP and TCP sockets with
> respect to IPv4 mapped addresses by calling IPv4 raw_sendmsg from
> rawv6_sendmsg to send those messages out.
> 
> Signed-off-by: Travis Brown <travisb@arista.com>
> Signed-off-by: Ivan Delalande <colona@arista.com>

For RAW sockets this doesn't make any sense.

Especially when header-include is enabled, one expects the application
to provide an address-family appropriate protocol header in it's
buffer.

Which means ipv4 for ipv4 sockets and ipv6 for ipv6 sockets.

So we should interpret the request as an ipv6 one regardless of
whether the ipv6 destination is ipv4 mapped or not.

Thank you.