netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Haley <brian.haley@hp.com>
To: "Erich E. Hoover" <ehoover@mines.edu>
Cc: Linux Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v4 1/2] Implement IP_UNICAST_IF socket option.
Date: Tue, 07 Feb 2012 10:24:45 -0500	[thread overview]
Message-ID: <4F31423D.5060905@hp.com> (raw)
In-Reply-To: <1328590876-15980-1-git-send-email-ehoover@mines.edu>

On 02/07/2012 12:01 AM, Erich E. Hoover wrote:
> 
> The IP_UNICAST_IF feature is needed by the Wine project.  This patch implements the feature by setting the outgoing interface in a similar fashion to that of IP_MULTICAST_IF.  A separate option is needed to handle this feature since the existing options do not provide all of the characteristics required by IP_UNICAST_IF, a summary is provided below.
> 
> --- a/net/ipv4/af_inet.c
> +++ b/net/ipv4/af_inet.c
> @@ -375,6 +375,7 @@ lookup_protocol:
>  	sk->sk_protocol	   = protocol;
>  	sk->sk_backlog_rcv = sk->sk_prot->backlog_rcv;
>  
> +	inet->uc_index  = 0;
>  	inet->uc_ttl	= -1;
>  	inet->mc_loop	= 1;
>  	inet->mc_ttl	= 1;

sk_alloc() will zero the struct, so this is unnecessary.

> --- a/net/ipv4/udp.c
> +++ b/net/ipv4/udp.c
> @@ -917,6 +917,9 @@ int udp_sendmsg(struct kiocb *iocb, struct sock *sk, struct msghdr *msg,
>  		if (!saddr)
>  			saddr = inet->mc_addr;
>  		connected = 0;
> +	} else if (!ipc.oif) {
> +		ipc.oif = inet->uc_index;
> +		connected = 0;
>  	}

I don't think you want to clear 'connected' here.

-Brian

      reply	other threads:[~2012-02-07 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-07  5:01 [PATCH v4 1/2] Implement IP_UNICAST_IF socket option Erich E. Hoover
2012-02-07 15:24 ` Brian Haley [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=4F31423D.5060905@hp.com \
    --to=brian.haley@hp.com \
    --cc=ehoover@mines.edu \
    --cc=netdev@vger.kernel.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).