From: "David S. Miller" <davem@davemloft.net>
To: sri@us.ibm.com
Cc: netdev@vger.kernel.org, lksctp-developers@lists.sourceforge.net
Subject: Re: [PATCH 2/4] [SCTP]: Prevent possible infinite recursion with multiple bundled DATA.
Date: Fri, 05 May 2006 17:04:17 -0700 (PDT) [thread overview]
Message-ID: <20060505.170417.47696523.davem@davemloft.net> (raw)
In-Reply-To: <1146856478.7861.34.camel@w-sridhar2.beaverton.ibm.com>
From: Sridhar Samudrala <sri@us.ibm.com>
Date: Fri, 05 May 2006 12:14:38 -0700
> [SCTP]: Prevent possible infinite recursion with multiple bundled DATA.
>
> There is a rare situation that causes lksctp to go into infinite recursion
> and crash the system. The trigger is a packet that contains at least the
> first two DATA fragments of a message bundled together. The recursion is
> triggered when the user data buffer is smaller that the full data message.
> The problem is that we clone the skb for every fragment in the message.
> When reassembling the full message, we try to link skbs from the "first
> fragment" clone using the frag_list. However, since the frag_list is shared
> between two clones in this rare situation, we end up setting the frag_list
> pointer of the second fragment to point to itself. This causes
> sctp_skb_pull() to potentially recurse indefinitely.
>
> Proposed solution is to make a copy of the skb when attempting to link
> things using frag_list.
>
> Signed-off-by: Vladislav Yasevich <vladsilav.yasevich@hp.com>
> Signed-off-by: Sridhar Samudrala <sri@us.ibm.com>
Applied, but again I had to manually remove a ton of trailing
whitespace added by this patch.
prev parent reply other threads:[~2006-05-06 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 19:14 [PATCH 2/4] [SCTP]: Prevent possible infinite recursion with multiple bundled DATA Sridhar Samudrala
2006-05-06 0:04 ` David S. 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=20060505.170417.47696523.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=lksctp-developers@lists.sourceforge.net \
--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