The comment about sctp_sf_violation_paramlen() is wrong. Invalid length should be identified as it does not equal actual length of a given parameter. The actual length of a given parameter is not including the padding part. Signed-off-by: Shan Wei <shanwei@xxxxxxxxxxxxxx> --- net/sctp/sm_statefuns.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/net/sctp/sm_statefuns.c b/net/sctp/sm_statefuns.c index edb71e6..8774a6e 100644 --- a/net/sctp/sm_statefuns.c +++ b/net/sctp/sm_statefuns.c @@ -4355,8 +4355,8 @@ static sctp_disposition_t sctp_sf_violation_chunklen( /* * Handle a protocol violation when the parameter length is invalid. - * "Invalid" length is identified as smaller than the minimal length a - * given parameter can be. + * "Invalid" length is identified as it does not equal actual length + * of a given parameter. */ static sctp_disposition_t sctp_sf_violation_paramlen( const struct sctp_endpoint *ep, -- 1.6.3.3 -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
