mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: wcang@nav6.org
To: netdev@vger.kernel.org, maxk@qualcomm.com
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] NET: Proper handling of IPv6 header in tun driver when  TUN_NO_PI is set
Date: Fri, 6 Jun 2008 20:13:38 +0800 (MYT)	[thread overview]
Message-ID: <59966.10.207.160.229.1212754418.squirrel@nav6.org> (raw)

By default, tun.c running in TUN_TUN_DEV mode will set the protocol of packet
to IPv4 if TUN_NO_PI is set. My program failed to work when I assumed that
the driver will check the first nibble of packet, determine IP version and set
the appropriate protocol.

The test for this change was conducted on 2.6.24.7 kernel. But the diff is
produced using git commit
c3b25b32e8bef526cca748e1ba023c6bdd705a99. I couldn't test it on kernel version
greater than 2.6.25 due to out of tree driver failing to compile. But
tun_get_user doesn't change that much between 2.6.24 and 2.6.26, so it should
work, I hope :-D . This patch is trivial because this problem can also be fixed
by not using TUN_NO_PI.

Signed-off-by: Ang Way Chuang <wcang@nav6.org>
---

diff --git a/drivers/net/tun.c b/drivers/net/tun.c
index 0ce07a3..77964bc 100644
--- a/drivers/net/tun.c
+++ b/drivers/net/tun.c
@@ -313,6 +313,21 @@ static __inline__ ssize_t tun_get_user(struct tun_struct *tun, struct iovec *iv,

        switch (tun->flags & TUN_TYPE_MASK) {
        case TUN_TUN_DEV:
+               if (tun->flags & TUN_NO_PI) {
+                       switch (skb->data[0] & 0xf0) {
+                       case 0x40:
+                               pi.proto = __constant_htons(ETH_P_IP);
+                               break;
+                       case 0x60:
+                               pi.proto = __constant_htons(ETH_P_IPV6);
+                               break;
+                       default:
+                               tun->dev->stats.rx_dropped++;
+                               kfree_skb(skb);
+                               return -EINVAL;
+                       }
+               }
+
                skb_reset_mac_header(skb);
                skb->protocol = pi.proto;
                skb->dev = tun->dev;

-- 


             reply	other threads:[~2008-06-06 11:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 12:13 wcang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-06-06 10:49 Ang Way Chuang
2008-06-06 20:21 ` Max Krasnyanskiy
2008-06-06 20:48   ` Stephen Hemminger
2008-06-17 23:32   ` David Miller
2008-06-18  2:13     ` Ang Way Chuang
2008-06-18  4:08       ` David Miller
2008-06-24  5:09         ` Max Krasnyansky

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=59966.10.207.160.229.1212754418.squirrel@nav6.org \
    --to=wcang@nav6.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maxk@qualcomm.com \
    --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

all inboxes | Powered by JetHome®