From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Sridhar Samudrala <sri@us.ibm.com>,
David Miller <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [SCTP]: Always linearise packet on input
Date: Tue, 31 Oct 2006 09:36:54 -0500 [thread overview]
Message-ID: <45475F86.6050309@hp.com> (raw)
In-Reply-To: <20061031030110.GA27427@gondor.apana.org.au>
Herbert Xu wrote:
> Hi Sridhar:
>
> On Mon, Oct 30, 2006 at 05:31:24PM -0800, Sridhar Samudrala wrote:
>> I think we currently assume atleast the SCTP header and the data
>> chunk header to be in the skb head.
>> But we do handle skbs with data in the frag_list.
>> Not sure about skb's with paged fragments.
>
> You can't assume the chunk header to be in the head. Think about what
> happens when some malicious person sends you a fragmented SCTP packet.
>
>> Does XEN use frag_list or frags array?
>
> Xen creates paged frags in domU=>dom0 or domU=>domU traffic.
> Of course frag_list can always occur as a result of IP fragmentation.
>
>> Is there a simple way to simulate incoming packets with transport
>> headers and data in skb's frag_list/pages without having to use XEN.
>
> You can use IP fragments to create them.
>
> But the important thing is to work through the code. Basically wherever
> you see things like skb_pull/skb->data without a preceding pskb_may_pull
> call, then you have a problem.
Wouldn't this in the end be equivalent to skb_linearize()? I am trying to
think of a way do things without reallocating too much memory.
Yes, SCTP is really broken with regard to fragmented skbs. In fact, I
have a test case that will crash the lksctp at will when receiving an IP fragmented
message.
The reason pskb_may_pull() is not a great solution IMO, is because we
may end up doing very large orders of allocations if someone decided to use 9000 MTU
on the first hop. I can see things going bad on loopback with 16K MTU as well.
-vlad
next prev parent reply other threads:[~2006-10-31 14:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 7:11 [SCTP]: Always linearise packet on input Herbert Xu
2006-10-30 7:46 ` David Miller
2006-10-31 1:31 ` Sridhar Samudrala
2006-10-31 3:01 ` Herbert Xu
2006-10-31 14:36 ` Vlad Yasevich [this message]
2006-10-31 18:18 ` Sridhar Samudrala
2006-10-31 18:46 ` Vlad Yasevich
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=45475F86.6050309@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=sri@us.ibm.com \
/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).