netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: hadi@cyberus.ca
Cc: "David S. Miller" <davem@davemloft.net>,
	netdev@oss.sgi.com, Wichert Akkerman <wichert@wiggy.net>
Subject: Re: patch: tunnels not setting inputdev
Date: Fri, 31 Dec 2004 19:02:04 +0100	[thread overview]
Message-ID: <41D5941C.8060001@trash.net> (raw)
In-Reply-To: <1104513392.1048.316.camel@jzny.localdomain>

jamal wrote:
> Dave,
> 
> Patch attached that has tunnels setting input dev correctly. 
> 
> Incorporates what ive sent to Wichert already.
> 
> A lot of the stuff the tunnels do is very similar, so maybe wiser to
> have something like tunnel_type_trans().
> 
> cheers,
> jamal
> 
> 
> ------------------------------------------------------------------------
> 
> --- 2610-bk1/net/ipv4/xfrm4_input.c	2004/12/31 17:00:25	1.1
> +++ 2610-bk1/net/ipv4/xfrm4_input.c	2004/12/31 17:01:05
> @@ -142,6 +142,7 @@
>  			dst_release(skb->dst);
>  			skb->dst = NULL;
>  		}
> +		skb->input_dev = skb->dev;

This is not necessary, xfrm4_input doesn't change anything
regarding devices, so if it was correct before, it is still
correct. For the remaining changes, why not simply set
input_dev in netif_receive_skb before the call to ing_filter ?


>  		netif_rx(skb);
>  		return 0;
>  	} else {

Another question - why is ing_filter exported when
CONFIG_NET_CLS_ACT is defined ? Nobody uses it currently
outside of dev.c.

Regards
Patrick

  reply	other threads:[~2004-12-31 18:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-31 17:16 patch: tunnels not setting inputdev jamal
2004-12-31 18:02 ` Patrick McHardy [this message]
2004-12-31 20:11   ` jamal
2005-01-01 16:10     ` Patrick McHardy
2005-01-01 23:33       ` jamal
2005-01-02  0:24         ` Patrick McHardy
2005-01-03 14:46           ` jamal

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=41D5941C.8060001@trash.net \
    --to=kaber@trash.net \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    --cc=wichert@wiggy.net \
    /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).