From: David Miller <davem@davemloft.net>
To: netdev@vger.kernel.org
Subject: Re: [RFC PATCH] ipv6: Make IP6CB(skb)->nhoff 16-bit.
Date: Mon, 19 Jul 2010 22:01:43 -0700 (PDT) [thread overview]
Message-ID: <20100719.220143.233859017.davem@davemloft.net> (raw)
In-Reply-To: <20100715.223011.58409183.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Thu, 15 Jul 2010 22:30:11 -0700 (PDT)
>
> Even with jumbograms I cannot see any way in which we would need
> to records a larger than 65535 valued next-header offset.
>
> The maximum extension header length is (256 << 3) == 2048.
> There are only a handful of extension headers specified which
> we'd even accept (say 5 or 6), therefore the largest next-header
> offset we'd ever have to contend with is something less than
> say 16k.
>
> Therefore make it a u16 instead of a u32.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> Can anyone find any holes in this? I want to do this so we
> can legitimately rip ndisc_nodetype out of struct sk_buff
> and stick it into the IP6CB where it belongs. Currently
> there isn't enough space, but with this change there will
> be.
No holes claimed by anyone, so... applied :-)
prev parent reply other threads:[~2010-07-20 5:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 5:30 [RFC PATCH] ipv6: Make IP6CB(skb)->nhoff 16-bit David Miller
2010-07-20 5:01 ` David Miller [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=20100719.220143.233859017.davem@davemloft.net \
--to=davem@davemloft.net \
--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).