netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kunihiro Ishiguro <kunihiro@ipinfusion.com>
To: Kazunori MIyazawa <Kazunori.Miyazawa@jp.yokogawa.com>
Cc: netdev@oss.sgi.com, usagi-core@linux-ipv6.org, davem@redhat.com,
	kuznet@ms2.inr.ac.ru
Subject: Re: [PATCH] IPv6 IPsec support
Date: Tue, 18 Feb 2003 21:57:39 -0800	[thread overview]
Message-ID: <87znos3j8s.wl@ipinfusion.com> (raw)
In-Reply-To: <20030219134850.5f203ea7.Kazunori.Miyazawa@jp.yokogawa.com>

I just look through the patch.  Here is my quick comments.

I think no need of broadcasting my comments to kernel ML, so I took it
of from CC:.  netdev guys will be interested in right?  So I kept it.

1. Do we really need to remove AH header from skb?

In case of IPv4 we modify iph->protocol for further processing thus AH
header is removed.  But in case of IPv6, we just simply authenticate
the packet then process next header.  So do we really need to remove
AH header in IPv6?  Remaining AH header does not harm...

2. Easy kmalloc()...

It seems there are some easy kmalloc().  Yes I'm stingy with memory.
Let's say no AH mutable option field in IPv6 extention headers
(actually it is very common case).  We just need char work_buf[8] to
retain IPv6 header mutable field.  But all the time the patch allocate
complete copy of the header including extention header then keep it in
the chamber....

+	int hdr_len = skb->h.raw - skb->nh.raw;
...
+	tmp_hdr = kmalloc(hdr_len, GFP_ATOMIC);

I think we should provision the need of mutation then allocate exactly
required memory.  If there no need of allocation, that's good news.
Let me provide code for it.

3. xfrm6_policy_lookup()

+		if (pol->family != AF_INET6) continue);

Last paren ;-).

Well, I'll find more.  Maybe we should be offline and come up with a
single patch.
-- 
Kunihiro Ishiguro

  parent reply	other threads:[~2003-02-19  5:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-19  4:48 [PATCH] IPv6 IPsec support Kazunori MIyazawa
2003-02-19  4:50 ` David S. Miller
2003-02-19  5:10   ` Kunihiro Ishiguro
2003-02-19  5:17     ` Mitsuru KANDA / 神田 充
2003-02-19  5:58       ` Kazunori Miyazawa
2003-02-19  5:30   ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-19  5:57 ` Kunihiro Ishiguro [this message]
2003-02-19  7:02   ` David S. Miller
2003-02-19  9:13     ` Kunihiro Ishiguro
2003-02-19  7:13 ` David S. Miller
2003-02-19  7:33 ` David S. Miller
2003-02-19 14:39   ` (usagi-core 11926) " Kazunori MIyazawa
2003-02-19 21:27     ` David S. Miller
2003-02-19 16:56   ` Mitsuru KANDA / 神田 充
2003-02-19 21:43     ` David S. Miller
2003-02-19 23:10     ` Kunihiro Ishiguro
2003-02-20  0:37       ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2003-02-22 11:26 [PATCH] IPv6 IPSEC support Kazunori Miyazawa
2003-02-22 11:13 ` David S. Miller
2003-02-22 12:15   ` Kazunori Miyazawa
2003-02-22 12:49   ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-22 23:47     ` David S. Miller
2003-02-23  0:44       ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-23 15:35   ` Kazunori Miyazawa

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=87znos3j8s.wl@ipinfusion.com \
    --to=kunihiro@ipinfusion.com \
    --cc=Kazunori.Miyazawa@jp.yokogawa.com \
    --cc=davem@redhat.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=netdev@oss.sgi.com \
    --cc=usagi-core@linux-ipv6.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).