sctp: Fix SCTP_MAXSEG socket option to comply to spec.

Browse source

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>

...

This commit is contained in:

Vlad Yasevich 2009-09-04 18:21:00 -04:00

parent cb95ea32a4

commit f68b2e05f3

4 changed files with 11 additions and 14 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

7

include/net/sctp/sctp.h

View file

1

include/net/sctp/structs.h

View file