diff options
| author | Vlad Yasevich <vladislav.yasevich@hp.com> | 2009-09-04 18:21:00 -0400 |
|---|---|---|
| committer | Vlad Yasevich <vladislav.yasevich@hp.com> | 2009-09-04 18:21:00 -0400 |
| commit | f68b2e05f326971cd76c65aa91a1a41771dd7485 (patch) | |
| tree | 2940d83f3787570cc030791378ee23b89b941662 /kernel/module.c | |
| parent | cb95ea32a457871f72752164de8d94fa20f4703c (diff) | |
| download | kernel_samsung_smdk4412-f68b2e05f326971cd76c65aa91a1a41771dd7485.zip kernel_samsung_smdk4412-f68b2e05f326971cd76c65aa91a1a41771dd7485.tar.gz kernel_samsung_smdk4412-f68b2e05f326971cd76c65aa91a1a41771dd7485.tar.bz2 | |
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>
Diffstat (limited to 'kernel/module.c')
0 files changed, 0 insertions, 0 deletions