From: Vlad Yasevich <vladislav.yasevich@hp.com>
Date: Fri, 4 Sep 2009 22:21:00 +0000 (-0400)
Subject: sctp: Fix SCTP_MAXSEG socket option to comply to spec.
X-Git-Tag: v2.6.32-rc1~703^2~61
X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=f68b2e05f326971cd76c65aa91a1a41771dd7485;p=pandora-kernel.git

sctp: Fix SCTP_MAXSEG socket option to comply to spec.

We had a bug that we never stored the user-defined value for
MAXSEG when setting the value on an association.  Thus future
PMTU events ended up re-writing the frag point and increasing
it past user limit.  Additionally, when setting the option on
the socket/endpoint, we effect all current associations, which
is against spec.

Now, we store the user 'maxseg' value along with the computed
'frag_point'.  We inherit 'maxseg' from the socket at association
creation and use it as an upper limit for 'frag_point' when its
set.

Signed-off-by: Vlad Yasevich <vladislav.yasevich@hp.com>
---

Reading git-diff-tree failed